feat(codemode): configurable max execution timeout#117
Merged
spachava753 merged 1 commit intomainfrom Dec 20, 2025
Merged
Conversation
Allow users to configure the maximum execution timeout for code mode via the `maxTimeout` field in `CodeModeConfig`. This addresses the limitation where the timeout was hardcoded to 300 seconds (5 minutes), which might be insufficient for long-running tasks like analyzing large codebases or running extensive tests. The `execute_go_code` tool definition now dynamically reflects the configured maximum timeout in its schema description and validation limits. The default behavior remains 300 seconds if the configuration is omitted or set to 0. Closes #114
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.
Allow users to configure the maximum execution timeout for code mode via the
maxTimeoutfield inCodeModeConfig. This addresses the limitation where the timeout was hardcoded to 300 seconds (5 minutes), which might be insufficient for long-running tasks like analyzing large codebases or running extensive tests.The
execute_go_codetool definition now dynamically reflects the configured maximum timeout in its schema description and validation limits. The default behavior remains 300 seconds if the configuration is omitted or set to 0.Closes #114