Repository navigation
Continue in New Session loses handoff when Codex self-updates #18153
Description
Reproduction
- Have Codex CLI report an available update on startup.
- In an existing Codex pane, click Continue in New Session….
- Keep Codex selected and click Start New Session.
- Choose Update now in Codex's startup update prompt.
Actual behavior
Codex installs the update and exits with its “Please restart Codex” message. The one-shot launch is consumed before Orca can deliver the generated continuation prompt, so the new session never starts with the prior session context.
Expected behavior
Context-bearing continuation launches should reach the Codex composer and submit their prepared handoff. Codex can continue checking for updates on ordinary launches, where an update does not discard a pending Orca action.
Notes
This affects the reported toolbar action and the equivalent continuation actions elsewhere in Orca. It can reproduce on any execution host where Codex offers its interactive startup updater, including SSH/WSL hosts.
Activity
luisgonzaleznf commentedon Sep 21, 2026
The fix PR — #18156 — had drifted into merge conflicts and is now resolved and back to
MERGEABLE(merged currentmainin atf49b6f8a03, 1588 commits behind).The PR's own diff is unchanged at 7 files; the conflicts were two lines where main's new
promptDeliveryrouting met this PR'ssuppressStartupUpdatePrompt, and both sides were kept. Typecheck and the 172 launch/startup tests pass.It has no reviewer assigned — it is unblocked and ready whenever someone can take it.
fix(agents): skip Codex's startup update prompt on Orca-driven launch…