"Codex stopped working" can describe several different failures: the desktop app or CLI cannot authenticate, a request receives an unexpected 429, a cloud task or review depends on GitHub, or one local session stalls while OpenAI remains healthy.

Fast answer: check OpenAI Status for Codex incidents, then preserve local work before signing out, clearing state, or repeatedly retrying the same request.

Match the Codex error before choosing a fix.

Codex symptomWhat it may meanBest first move
Access denied in Codex desktop or CLIAuthentication or service-side access incidentCheck Codex status before changing credentials
Unexpected HTTP 429Rate limit, quota, or provider-side rate-limiting failureRecord the exact response and check OpenAI incidents
Code review or web task failsCodex or GitHub-dependent workflow degradationCheck both service dependencies and preserve task state
One local session hangsShell, tool call, context, or local process issueInspect terminal output and repository changes
Request fails after editsPartial execution with an incomplete responseVerify the diff before sending the prompt again

Official incidents confirm these are distinct Codex failures.

OpenAI documented a July incident where some Codex desktop and CLI users received access-denied errors. Another incident produced unexpected HTTP 429 responses for Codex requests. GitHub-dependent ChatGPT and Codex workflows have also failed or been delayed when GitHub services were degraded.

The same "Codex is down" search can therefore lead to three different actions: wait for OpenAI, wait for a dependency, or repair a local session.

What to do when Codex stops working mid-task.

  1. Copy the exact error code and affected Codex surface.
  2. Check OpenAI Status for Codex and related components.
  3. Stop retry loops that may duplicate commands or edits.
  4. Capture git status, git diff, changed files, and terminal output.
  5. Record which commands actually completed and which tests actually passed.
  6. Resume in a fresh Codex session or continue in another supported AI tool.

Unexpected 429 does not always mean you used the quota.

A 429 commonly means rate limiting, but OpenAI's June incident report says Codex requests were incorrectly rejected with HTTP 429 responses because of a service configuration problem. Preserve the full response and check status before assuming the account needs more credits or waiting for a normal reset.

How ShardStitch helps after a failed Codex request.

ShardStitch reconstructs the task from repository evidence, project memory, decisions, failed attempts, test output, and dependency risk. It labels unverifiable statements as inferred and creates a continuation packet for Codex or another supported target.

This avoids forcing the next agent to rediscover the repository or blindly trust a partial Codex response. The next action starts from what is known, what remains uncertain, and what should be verified first.

Related Codex and outage guides.