Codex Hanging while working

Resolved 💬 14 comments Opened Nov 5, 2025 by randynov Closed Nov 16, 2025
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex is running?

codex-cli 0.55.0

What subscription do you have?

Plus

Which model were you using?

gpt-5-codex

What platform is your computer?

Darwin 24.6.0 arm64 arm

What issue are you seeing?

No errors, just kept spinning. Over 35m with 6 retries and no progress or updates.

What steps can reproduce the bug?

Uploaded thread: 019a5593-be88-7a50-9c5e-9e218ba9664c

What is the expected behavior?

Some kind of visible progress or action so it's clear whether it is working or not.

Additional information

_No response_

View original on GitHub ↗

14 Comments

github-actions[bot] contributor · 8 months ago

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

  • #6280
  • #6279
  • #6278
  • #6277
  • #6274

Powered by Codex Action

randynov · 8 months ago

Seems the temporary service outage is not fully resolved, I am still experiencing the issue.

lihaoml · 8 months ago

same here

etraut-openai contributor · 8 months ago

If you're still seeing problems, then it's probably not related to the service outage from earlier today. Reopening.

Have you tried logging out and logging in again? It would be interesting to understand if that fixes the problem.

etraut-openai contributor · 8 months ago

@randynov & @lihaoml, do you have any other atypical / non-default codex configuration settings?

Bryan-Nsoh · 8 months ago

Same this has been the most persistent adn annoying issue: 019a5649-520a-7592-b6bc-307a09a12ce0

randynov · 8 months ago

@etraut-openai I don't think so, happy to provide any details / files you want.

etraut-openai contributor · 8 months ago

Did this behavior start just after you upgraded to 0.55.0? If you downgrade to 0.53.0, does that restore functionality? I'm trying to determine if this was a regression in the CLI (versus a service issue, for example).

Bryan-Nsoh · 8 months ago
Did this behavior start just after you upgraded to 0.55.0? If you downgrade to 0.53.0, does that restore functionality? I'm trying to determine if this was a regression in the CLI (versus a service issue, for example).

For my case it has been happening since September which is when i started using codex cli. I am on the most recent update. The issue persists. Hard to say if it has gotten any worse. Codex just needs better strategies for running long running commands and not randomly hanging in the middle of the conversation

jakenuts · 8 months ago

I've noticed similar behavior though without the response or indication of progress, just nods off after a couple successful prompts. Occasionally it will say "I will definitely do that" and then just waits. This is usually at the tail end of large sessions so it could be context compaction or issues with that process.

randynov · 8 months ago

@etraut-openai FYI, I logged out and back in to resume the same thread. No further issues.

kjhenner · 8 months ago

I was having both apparent hanging and periodic "reconnecting" issues. It seems to have been related to having multiple instances of the tool open in different issues, as restarting/logging out for one instance didn't help, but closing all instances seems to have resolved it--for the moment, at least! Intuitively, it makes sense that multiple instances could have prevented whatever token or state needed to be reset from being reset.

edzme · 8 months ago

<img width="571" height="35" alt="Image" src="https://github.com/user-attachments/assets/ae942eca-7775-4902-8f62-f0fe81c09804" />

Having this issue on Codex (v0.58.0)
thread id: 019a88f5-3882-7e12-84db-22852e109b16
Unlike some others here I've never experienced it before today.

edit: downgraded to v0.53.0, the issue is not on that version.

etraut-openai contributor · 8 months ago

There are several different symptoms discussed above. I'm going to close this issue, but if you see a similar issue, please use the /feedback slash command in the CLI to log a new issue.