codex icon indicating copy to clipboard operation
codex copied to clipboard

Ability to configure bash command timeout limit

Open HeroBrian389 opened this issue 3 months ago • 4 comments

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 out

It 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

HeroBrian389 avatar Sep 08 '25 00:09 HeroBrian389

The model should be able to adjust this. Have you tried giving it more context into this?

aibrahim-oai avatar Sep 08 '25 23:09 aibrahim-oai

I have implement this you can adjust by using slash command /configuration

Check out this fork https://github.com/thammachet/hopefully-better-codex

thammachet avatar Sep 10 '25 12:09 thammachet

I can't seem to run any command that takes longer than 10s, it's infuriating.

shrx avatar Nov 19 '25 23:11 shrx

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!

rahidz avatar Dec 01 '25 11:12 rahidz