fix(config): increase default chat timeout#105
Open
owainlewis wants to merge 1 commit 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.
Summary
run_timeoutoverrides.Why
Research and multi-tool Codex requests were repeatedly terminated at the exact 120-second default, including a request that researched AI news and created a Passage document. Ten minutes gives normal agent workflows enough time while keeping a finite bound.
Test plan
cargo test(257 tests passed)cargo clippy --all-targets -- -D warningscargo fmt --checkRisks
Slow or stuck chat runs can now occupy a worker for up to 10 minutes by default. Users can set a shorter explicit
run_timeout.Related issue
None.