Add agents.interrupt_message for interruption markers#19351
Merged
Conversation
jif-oai
changed the title
Collaborator
Author
|
@codex review |
Contributor
|
Codex Review: Didn't find any major issues. Delightful! ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Collaborator
Author
|
@codex review |
Contributor
|
Codex Review: Didn't find any major issues. Can't wait for the next one! ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Why
Agent interruptions currently always persist a model-visible interrupted-turn marker before emitting
TurnAborted. That marker is useful by default because it gives the next model turn context about a deliberately interrupted task, but some deployments need to suppress that history injection entirely while still keeping the client-visible interruption event.What changed
[agents] interrupt_message = falseto disable the model-visible interrupted-turn marker.Config::agent_interrupt_message_enabled, defaulting totrueso existing behavior is unchanged.TurnAbortedeven when the history marker is disabled.core/config.schema.jsonfor the newagents.interrupt_messagefield.Testing
cargo test -p codex-core load_config_resolves_agent_interrupt_message -- --nocapturecargo test -p codex-core disabled_interrupted_fork_snapshot_appends_only_interrupt_event -- --nocapturecargo test -p codex-core multi_agent_v2_interrupted_marker_uses_developer_input_message -- --nocapturecargo test -p codex-core multi_agent_v2_followup_task_can_disable_interrupted_marker -- --nocapturecargo test -p codex-core multi_agent_v2_followup_task_interrupts_busy_child_without_losing_message -- --nocapturecargo check -p codex-core