feat: auto-continue after server overload - #16
Open
AVas112 wants to merge 2 commits into
Open
Conversation
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
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.
What changed
Continueafter aServerOverloadederror.ServerOverloadedis kept separate fromUsageLimitExceeded, preserving the existing usage-limit behavior.Continueentries are prevented by deduplicating the locally rendered prompt and its app-server echo using bothturn_idand message content.Why
When the selected model is overloaded, the current turn ends with
Selected model is at capacity. Previously, the user had to submit a continuation manually. Codext now starts the next turn automatically so work can continue without manual intervention.Configuration
Auto-continuation is enabled by default. To disable it, add the following to
config.toml:Validation
cargo build -p codex-clicargo build --release -p codex-cligit diff --checkTests and snapshot files were not changed, in accordance with the temporary
rust-v0.145.0reapply guardrails.