›_ Codex Issues
Codex Issues / #12595

CLI: network drop during Thinking/Working shows no immediate disconnect indicator

Open 💬 3 comments Opened Feb 23, 2026 by ClarkOhlenbusch
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex CLI is running?

codex-cli 0.104.0

What subscription do you have?

Team

Which model were you using?

codex 5.3 xhigh (seen while the agent is in Thinking/Working)

What platform is your computer?

Darwin 25.1.0 arm64 arm

What terminal emulator and version are you using (if applicable)?

Apple Terminal (TERM_PROGRAM=Apple_Terminal, TERM=xterm-256color)

What issue are you seeing?

If internet connectivity drops while an active turn is still Thinking/Working, there is no immediate on-screen indication that the connection was lost. The UI keeps showing Thinking/Working as if the turn were progressing normally. This continues indefinitely.

What steps can reproduce the bug?

  1. Start Codex CLI and submit a prompt that keeps the turn active for several seconds.
  2. While the status row shows Thinking/Working, disable internet connectivity (for example, turn Wi-Fi off).
  3. Wait a bit (optionally re-enable connectivity).
  4. Observe that the status can continue to show Thinking/Working without an immediate disconnect/reconnect indication.

What is the expected behavior?

When stream/transport connectivity is lost mid-turn, the CLI should promptly show an explicit status (for example Reconnecting... or Connection lost) instead of only showing Thinking/Working.

Additional information

  • This is different from resume-specific stale Working bugs; this report is about a live active turn when connectivity drops.
  • Possibly related issues:
  • #12382 (resume can get stuck on Working after unclean disconnect)
  • #12548 (reconnecting loop until timeout)
  • #11680 (stream disconnect while working with retries)
  • User impact: it looks like normal model progress even when transport has already dropped.

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 6 months ago

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

  • #12548
  • #11680
  • #11852

Powered by Codex Action

terryjyu · 6 months ago

Also experienced this multiple times after network disconnection. codex-cli 0.104.0 in linux

fortunexbt · 4 months ago

@ClarkOhlenbusch this is the fake-progress failure operators hate — transport dies mid-turn, the CLI keeps showing Thinking or Working as if the run were alive, and there is zero indication the connection dropped. The operator assumes work is progressing while the session is already dead.

That is the worst class of runtime lie because it defeats every health-check pattern an operator could build on top.

Are you more blocked by detecting transport loss immediately so the run can be recovered, or by controls that pause the session and surface what actually happened before the operator wastes time waiting on a dead turn?