fix: timeouts

Resolved 💬 6 comments Opened Feb 3, 2026 by Daanvdplas Closed Mar 29, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

Codex often uses timeouts which is very unproductive when something just takes long (e.g. compiling or installing something). It starts doing something, time outs, tries again with longer timeout, time outs, very unproductive. It would be very nice if this can be fixed.

View original on GitHub ↗

6 Comments

github-actions[bot] contributor · 5 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #9306
  • #8972
  • #10070

Powered by Codex Action

etraut-openai contributor · 5 months ago

Codex needs to impose timeouts on tool calls to prevent hangs, monitor tool progress, etc.

Can you say more about the problem you're seeing and what you're proposing as a solution? It's not clear what it would mean to "fix this".

If you have specific examples, it would be useful if you could use the /feedback tool to upload the session and post the thread ID.

Daanvdplas · 5 months ago

I run a test but it is taking more than 20 minutes, often timeouts and has to run again
I ask a subagent to work on something but it is taking longer, timeout

Kreijstal · 5 months ago

right now the timeout to check is too low, how to adjust it? when it runs a background job?

etraut-openai contributor · 3 months ago

This feature request hasn't received enough upvotes, so I'm closing it.

Kreijstal · 3 months ago

Rip