Codex can't run commands longer than 1 second

Open 💬 6 comments Opened Nov 20, 2025 by srogatch

💡 Likely answer: A maintainer (tibo-openai, collaborator) responded on this thread — see the highlighted reply below.

Codex used to run tests for me and check their results. But not anymore: now it says there's the CLI harness that aborts long-running commands, longer than 1 second. Please, confirm if there's indeed such a timeout in Codex CLI.

View original on GitHub ↗

6 Comments

rahidz · 9 months ago

I'm seeing the same behavior, but for me it's 10 seconds. Just started today. Very odd.

!Image

tibo-openai collaborator · 7 months ago

Which model do you use and could you try whether this also is a problem with the new background terminal feature which you can enable in /experimental?

srogatch · 7 months ago

It's not reproducible for me in Codex v0.77.0 . The tool waits for like half-an-hour long commands without issues.

rahidz · 7 months ago

Likewise here! The background terminal process works great!

sharno · 7 months ago

I wanted codex to wait for 15 minutes using a sleep command to gain back control and continue working. I tried with and without the background terminal and it cannot wait more than 10 seconds.

I'm using 5.2 codex model on medium effort. Using codex 0.77 as well

melsharnou-chwy · 7 months ago

Found the issue, seems that tool calls by default timeout after 10 seconds. The model has to call the tool with a timeout_ms parameter to be able to let the command finish