You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A clean build + test in my repo takes more than 2 minutes, and I could easily see it growing to more than 10 minutes for some tasks. I am seeing timeouts in the bash tool command often. Even with hints, it is often forgetting to set the timeout parameter (as far as I can tell)
My preferred fix:
default timeout is no timeout (runs forever)
max timeout is very long (1 day? infinite?)
Happy to submit a PR if this would be welcome.
Reacted by Caesar LaVey, Eron Wright, Jeff Verkoeyen, Mauricio Scheffer and Andrey Baksalyar
been using #1811 for a while now and its definitely better. Meanwhile I am working on a bash MCP to try and give the LLM full control over long running commands https://github.com/xhuw/async-bash-mcp
I think normally the concern tho is an agent will start a server or something itself and when it is looping itself it gets stuck, and a lot of people dont want that
which timeout are u wanting to set? The default? @rekram1-node
Yes, I want to re-set the default bash tool for my building task that lasts up to one hour or more
I think you can refer to claude code which has BASH_DEFAULT_TIMEOUT_MS & BASH_MAX_TIMEOUT_MS environment variables, they are can be set in the setting.json file.
Activity
xhuw commentedon Aug 18, 2025
been using #1811 for a while now and its definitely better. Meanwhile I am working on a bash MCP to try and give the LLM full control over long running commands https://github.com/xhuw/async-bash-mcp
junmediatek commentedon Nov 17, 2025
hi @thdxr @xhuw
Could you fix this issue?
default timeout is no timeout (runs forever)
max timeout is very long (1 day? infinite?)
rekram1-node commentedon Nov 18, 2025
We could prolly change it hmm
rekram1-node commentedon Nov 18, 2025
I think normally the concern tho is an agent will start a server or something itself and when it is looping itself it gets stuck, and a lot of people dont want that
junmediatek commentedon Dec 9, 2025
hi @rekram1-node
Is there anything for this issue?
rekram1-node commentedon Dec 9, 2025
I actually merged something for this @junmediatek it will be in next release:
default timeout will be 2 min, max timeout is gone (no cap)
junmediatek commentedon Dec 9, 2025
Hi @rekram1-node
I find the source code, however, how to set the bash tool timeout by opencode.json?
rekram1-node commentedon Dec 9, 2025
which timeout are u wanting to set? The default?
junmediatek commentedon Dec 9, 2025
Kreijstal commentedon Dec 9, 2025
how to increase timeout I want to have 20 hour timeout
Kreijstal commentedon Dec 9, 2025
opencode timeouts are incredibly obnoxious
junmediatek commentedon Dec 9, 2025
hi @Kreijstal
I think you can refer to claude code which has BASH_DEFAULT_TIMEOUT_MS & BASH_MAX_TIMEOUT_MS environment variables, they are can be set in the setting.json file.
rekram1-node commentedon Dec 9, 2025
in next release we will have
OPENCODE_EXPERIMENTAL_BASH_DEFAULT_TIMEOUT_MSPSU3D0 commentedon Dec 31, 2025
@rekram1-node can you add per tool timeouts? Some HITL tools might take days to get an "approval"
jverkoey commentedon Jan 25, 2026
Did OPENCODE_EXPERIMENTAL_BASH_DEFAULT_TIMEOUT_MS end up getting merged in to prod?
jnd0 commentedon Jan 27, 2026
I can see the
OPENCODE_EXPERIMENTAL_BASH_DEFAULT_TIMEOUT_MSis defined in the CLI docs as experimental.My default for running tasks was 2 mins.
If you have trouble with a specific command you can also ask the agent to pass a custom timeout for the bash tool call.
github-actions commentedon Mar 29, 2026
To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.
fix(app): collapse redundant Tailwind axes (anomalyco#1721)