feat: per-scenario timeout override; chat-agent-advanced gets 600s#2
Open
ericallam wants to merge 1 commit into
Open
feat: per-scenario timeout override; chat-agent-advanced gets 600s#2ericallam wants to merge 1 commit into
ericallam wants to merge 1 commit into
Conversation
Scenarios can now set `timeoutMs` to override the global config default. The chat-agent-advanced scenario (sessions/HITL/sub-agents, the heaviest task) was hitting the 300s cap in both arms, so the run reflected the timeout, not the skill. Bump it to 600s.
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
Scenarios can set a
timeoutMsto override the global per-run default. Thechat-agent-advancedscenario (sessions / HITL / sub-agents, the heaviest task) was hitting the 300s cap in both arms, so its result reflected the timeout rather than the skill. It now gets 600s and completes.This came out of evaluating a trigger.dev change where the whole sweep was green except
chat-agent-advanced, which timed out identically in both arms. With 600s it completes, and the with-skills arm passes both samples.