Debug and fix detached Zellij launches for Codex tasks when session creation succeeds but the attached pane only shows a shell or no visible Codex UI.
Use when Hermes/botfiles pickup or launcher flows claim a Zellij session was started for a Codex task, but attaching shows only an idle shell, missing task metadata, or verification based only on zellij list-sessions.
A detached Zellij session existing is not sufficient evidence that Codex launched successfully. Verify a real visible pane and the Codex process/UI before treating the lane as active.
Inspect the ticket/session state
~/pro/personal_os for Arya ambiguous tickets).zellij list-sessionszellij action query-tab-names --session <session>zellij action dump-screen --session <session> -p <pane_id> -fCheck whether the launcher is over-crediting success
zellij list-sessions, that is insufficient.Validate --dry-run honestly
start-zellij-session-for-task --project-root <root> --dry-run <ISSUE>--dry-run unless the tool truly performs launch under dry-run.Fix detached launch behavior
options --default-shell <bootstrap> may not produce a visible pane that can be inspected.ZELLIJ_SESSION_NAME=<session> zellij run -- <bootstrap_path>terminal_1 that actually runs Codex.Strengthen verification
terminal_1 or returned pane) with dump-screen.OpenAI Codex$start-new-task <ISSUE>Normalize ticket state instead of broadening supervision
Todo, the cleaner approach is to move the ticket to In Progress.Todo live lanes.zellij list-sessions shows the sessionzellij action list-panes (or equivalent session inspection) shows a real running panedump-screen on the active pane shows Codex UI, not just a shell promptdump-screen against the wrong pane can make a healthy launch look broken.~/pro/botfiles as evidence of a task lane for another repo.