Handle exec shutdown on Interrupt (fixes immortal codex exec with websockets)
#10519
+14
−10
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
codex execexits when a running turn is interrupted (e.g., Ctrl-C) so the CLI is not "immortal" when websockets/streaming are used.Description
CodexStatus::InitiateShutdownwhen handlingEventMsg::TurnAbortedinexec/src/event_processor_with_human_output.rsso human-output exec mode shuts down after an interrupt.protocol::EventMsg::TurnAbortedasCodexStatus::InitiateShutdowninexec/src/event_processor_with_jsonl_output.rsso JSONL output mode behaves the same.just fmt.Testing
just fmtsuccessfully.cargo test -p codex-exec; many unit tests ran and the test command completed, but the full test run in this environment produced35 passed, 11 failedwhere the failures are due to Landlock sandbox panics and 403 responses in the test harness (environmental/integration issues) and are not caused by the interrupt/shutdown changes.Codex Task