Ability to configure bash command timeout limit
Resolved 💬 5 comments Opened Sep 8, 2025 by HeroBrian389 Closed Mar 20, 2026
💡 Likely answer: A maintainer (aibrahim-oai, contributor)
responded on this thread — see the highlighted reply below.
What feature would you like to see?
I want to add a section in configuration which allows users to manually set the command time out limit for commands that the agent runs.
This is most relevant in long running bash commands/scripts. I see messages like:
error: command timed outIt would be great to configure a general bash command timeout, and perhaps even a command-by-command timeout. E.g. we might want a specific bash script ./long_running_script.sh to run for 20 minutes+, but we may not want find to run for 20 minutes - I think the user would rather the agent get an error for this more quickly as a clue to try another approach.
Are you interested in implementing this feature?
_No response_
Additional information
_No response_
Showing cached comments. Read the full discussion on GitHub ↗
4 Comments
The model should be able to adjust this. Have you tried giving it more context into this?
I can't seem to run any command that takes longer than 10s, it's infuriating.
I wound up adding "IMPORTANT: YOU MUST USE TIMEOUT_MS = 600000 OR ELSE YOU WILL TIME OUT AT 10-15 SECONDS." to my AGENTS.md and that seems to have mostly helped, though it still forget maybe ~10% of the time.
Sidenote: Pulse, if you're reading this, thanks for alerting me to this thread!
As mentioned above, this is under control of the model, not something that makes sense to put in the configuration.