Taking a long time / doesn't answer

[sanjayss34]

What version of Codex is running?

0.58.0

What subscription do you have?

API

Which model were you using?

gpt-5-codex medium and gpt-5.1-codex medium

What platform is your computer?

Linux 6.14.0-33-generic x86_64 x86_64

What issue are you seeing?

Running for a very long time (20+ mins) without responding

What steps can reproduce the bug?

Uploaded thread: 019a7fc1-2ada-7a81-9db4-7151985d75cb

What is the expected behavior?

No response

Additional information

No response

[github-actions[bot]]

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

• #6519
• #6280
• #5885
• #6331
• #6277

Powered by Codex Action

[lulu-sk]

same

[TerminX]

Same here with a Pro account. It just sits there doing nothing for almost 14 minutes before beginning work at a seemingly normal pace. It's fundamentally the experience you'd get if someone's preferred method of debugging backend components that can't just have a debugger attached for their entire execution lifetime was to a log a message somewhere and spin in place for long enough to manually attach a debugger, and their preferred duration to wait was 13:37 because they thought it was funny.

[gravitydeepimpactsun]

I downgraded (npm install -g @openai/[email protected]), it's working now and I still have 5.1 models.

[kiptaylor]

Same here with a pro account.

[jarari]

Same here. It gets stuck after reading a file or two. Long thinking time, no context usage. Tested with an OpenAPI key. The issue persists in 0.59.0-alpha.5 as well.

[abronan]

Same issue, it's completely unusable at the moment (using codex from its early releases).

Using gpt-5.1-codex high with cli v0.58.0. It's not just an impression it really gets stuck with no replies, and if you escape/reprompt it sometimes completes the steps successfully in under a minute. You're essentially playing Russian roulette and sometimes it works, sometimes it doesn't. It's a frustrating experience.

edit: downgrading to v0.57.0 seems to be working so far as suggested in a comment above. So it looks like a regression on v0.58.0 and above.

[tylerstar]

Same here，stuck at 0.57 for now, I can only use gpt-5.1-codex-max high. I cannot use xhigh until problem was fixed

[abronan]

Issue still persists with ~v0.60.1~ v0.63.0. The first session went well, then on the second session it got stuck 20 minutes on the same step which should have been fast and I had to stop it. On the next try, it completed the same step/task in 55 seconds.

[IvoPereira]

Facing the same issue. Indeed downgrading to 0.57 makes it work.