How to increase the 120ms timeout for FunctionCall ?
Resolved 💬 8 comments Opened Jul 14, 2025 by helmus Closed Nov 2, 2025
💡 Likely answer: A maintainer (seratch, member)
responded on this thread — see the highlighted reply below.
What version of Codex is running?
~codex-cli 0.6.0~ codex-cli 0.9.0
Which model were you using?
gpt-4.1
What platform is your computer?
Darwin 24.5.0 arm64 arm
What steps can reproduce the bug?
Ask codex to run unit tests in a python / poetry project
run pytests using poetry
What is the expected behavior?
the unit tests should run for a reasonable amount of time ( 5 minutes ? )
What do you see instead?
the command times out immediately.
<img width="1249" height="233" alt="Image" src="https://github.com/user-attachments/assets/3de2b676-fc50-418d-a033-815dca665b9f" />
Additional information
log output. it looks like the timeout is set to 120ms.
How can we increase this timeout ?
2025-07-14T14:27:02.975975Z INFO FunctionCall: {"command":["poetry","run","pytest"],"timeout":120}
8 Comments
This is still an issue on 0.9.0
The latest version's timeout is 10 seconds, and if this pull request is merged in the future, you can customize the duration to be longer than 10 seconds. If you're still interested, trying the latest version (0.22.0) out would be appreciated. You can install the latest version by
npm -g i @openai/codex@latest.It still does not work on version
0.23.0, the time out occurs immediately. ( it works perfectly with claude code )<img width="647" height="154" alt="Image" src="https://github.com/user-attachments/assets/11e6c7a4-598e-468d-ae42-d8eeb400fe7f" />
@seratch This seems like the utmost basic functionality. How can I help get this fixed ?
Same issue. Web version has no problem.
Would be great if we can specify a timeout value in the config file
The PR is closed for some reason. Do we have a solution for the commands timeout issue?
I guess @seratch closed the PR because https://github.com/buihongduc132/codex/issues/3 seemed like it'd supplant/include it, but then that issue got closed too because the dev wasn't ready to tackle it?
Now I suppose we're in the tricky position where a proper redesign seems to be coming "at some point maybe" and any work before then might get wasted/have to be redone, but in the meantime the feature is left hanging.
I'm going to close this issue. It is pretty outdated at this point since it references the old (now retired) TypeScript version of Codex CLI. There are several other open issues that capture the idea of making tool call timeouts configurable. Here is one example. If you would like to see this added, please upvote one of these issues.