[Bug]: Codex sidebar entry disappears and shared-daemon hooks can target the wrong terminal

Versions

• Orca: 1.4.215
• Codex CLI and shared app-server daemon: 0.157.1 (both matched when reproduced)
• Current Codex CLI: 0.158.0; not yet retested on this version.

Summary

When launching Codex in Orca, the sidebar briefly shows Codex · Idle, then the entry disappears even though Codex remains running and accepts input.

A related issue occurs with multiple Codex terminals sharing an app-server daemon: hook status from a newer terminal can be attributed to the earlier terminal.

Reproduction

1. Launch Codex in an Orca terminal.
2. Wait for the input screen without submitting a prompt.
3. Observe that the sidebar's Codex entry appears briefly and disappears.
4. With an existing shared Codex daemon, launch another Codex terminal and submit a simple prompt.
5. Observe which terminal receives the resulting activity/completion status.

Expected

The sidebar retains the idle Codex entry while its process is running, and each session's hook events update its own terminal.

Findings

• The disappearing entry correlates with Codex changing its terminal title to the project name. Launching with the following override preserved the idle sidebar entry:

  bash复制

  codex -c 'tui.terminal_title=["app-name","spinner","project"]'

• For the hook attribution issue, the shared daemon retained the earlier terminal's ORCA_PANE_KEY, while the newer TUI process had its own correct value. A distinctive test reply in the newer terminal produced a Stop event attributed to the earlier terminal.

• A separate app-server process for the test terminal restored correct hook attribution.

• The title workaround does not establish that shared-daemon hook attribution is fixed.

These observations suggest that sidebar identity should survive terminal title changes, and hook-to-terminal attribution needs to account for a shared Codex daemon. The first affected release has not been identified.