Repository navigation
[FEATURE]: Configurable command timeout in config.json #3950
Description
- I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
The current 1-minute command timeout is too short for integration tests and other long-running operations. When running integration tests that may take longer than 1 minute, the timeout causes premature termination of commands.
Proposed Solution: Add a command_timeout setting to config.json that allows users to specify custom timeout duration.
Use Cases:
- Integration tests that take longer than 1 minute
- Build processes that require extended time
- Database migrations or other long-running operations
- CI/CD pipelines with extended execution times
Benefits:
- Flexibility for different project requirements
- Better support for long-running operations
- Improved developer experience for integration testing
- Maintains backward compatibility with existing setups
Metadata
Metadata
Assignees
Labels
No labels
Activity
github-actions commentedon Nov 5, 2025
This issue might be a duplicate of existing issues. Please check:
Feel free to ignore if none of these address your specific case.
rekram1-node commentedon Nov 5, 2025
@JosXa that's just the default timeout the agent can set it up to 10min currently. But yeah we could add an
experimentalsetting for this I think tools + permissions are going to be tweaked in the config so I'd prefer making an experimental flag for now until we have a better hierachyJosXa commentedon Nov 9, 2025
You're right, I can tell it explicitly to use a specific timeout 👍 Something to know, or maybe document
strk commentedon Nov 14, 2025
I'm having this problem at the /init stage, are you saying I can ask the model to raise the timeout BEFORE issuing the /init command ? It would indeed be useful to document how to change the timeout.
strk commentedon Nov 14, 2025
How ?
JosXa commentedon Nov 14, 2025
@strk Haven't tried, but intuitively I'd expect this to work:
"Whenever running terminal commands, use a timeout of 10 minutes.
/init"
rekram1-node commentedon Nov 14, 2025
@strk when the model calls bash commands there is an optional field for it to set a timeout, it can dynamically set that anytime it calls the tool.
abda11ah commentedon Nov 27, 2025
Hi, how to remove this timeout ?
The long running terminal commands are kicked after 60s
Please help
rekram1-node commentedon Nov 27, 2025
ill add some config for it but for now @abda11ah just tell the llm to give it a higher timeout when it runs it
JosXa commentedon Nov 28, 2025
@rekram1-node I noticed that the LLMs don't really get the idea that they can increase their command timeout parameter when it does time out. Could we add a note to the "this command expired" error that LLMs see along the lines of:
"This command timed out. If you believe that it just needs more time to complete and did not stuck in an interactive shell, feel free to increase the
timeoutparameter" (or whatever it's named). This way, we could even reduce the default to like 15 or 30 seconds and let it retry with a higher timeout when needed. It dropping into an interactive command would then not be such a big impact to total duration of the task.rekram1-node commentedon Dec 1, 2025
Yeah we could/should update the error message if the llms aren't listening good idea
rekram1-node commentedon Dec 9, 2025
we will have something more appropriate in the config later, for now we will have:
OPENCODE_EXPERIMENTAL_BASH_DEFAULT_TIMEOUT (supported in next release also this is in milliseconds)
peter-mw commentedon Mar 8, 2026
Any news on merging this ?
github-actions commentedon May 8, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.