Core: Pause pending steers after usage limits#22226
Open
ee-oai wants to merge 3 commits into
Open
Conversation
ee-oai
force-pushed
the
ee/pause-queue-sends-core
branch
2 times, most recently
from
cfd454b to
5880fd7
Compare
Co-authored-by: Codex <noreply@openai.com>
ee-oai
force-pushed
the
ee/pause-queue-sends-core
branch
from
5880fd7 to
cdfd8c6
Compare
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Core behavior for the paused queued-send stack.
Usage-limit-like failures no longer auto-send pending steers into the next turn. Instead, the core preserves queued follow-up state for the product surface to resolve explicitly, while keeping injected pending context behavior intact.
This is the base PR for the TUI follow-up in #22225 and the webview follow-up in https://github.com/openai/openai/pull/900729.
Validation: