"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.
Match the Codex error before choosing a fix.
| Codex symptom | What it may mean | Best first move |
|---|---|---|
| Access denied in Codex desktop or CLI | Authentication or service-side access incident | Check Codex status before changing credentials |
| Unexpected HTTP 429 | Rate limit, quota, or provider-side rate-limiting failure | Record the exact response and check OpenAI incidents |
| Code review or web task fails | Codex or GitHub-dependent workflow degradation | Check both service dependencies and preserve task state |
| One local session hangs | Shell, tool call, context, or local process issue | Inspect terminal output and repository changes |
| Request fails after edits | Partial execution with an incomplete response | Verify 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.
- Copy the exact error code and affected Codex surface.
- Check OpenAI Status for Codex and related components.
- Stop retry loops that may duplicate commands or edits.
- Capture git status, git diff, changed files, and terminal output.
- Record which commands actually completed and which tests actually passed.
- 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.