Agent says “overloaded” but I have usage left?
An overload message can describe service capacity even when your account still has usage available. Claude Code explicitly distinguishes 529 overload from your usage limit. Codex's “Selected Model is at Capacity” message has also appeared in an official service incident. Start with the exact error, then choose the matching recovery step.
Which message are you actually seeing?
Keep the complete error text and any reset time. Claude Code's error reference separates several cases:
- 529 Overloaded: the API is temporarily at capacity across users. The reference explicitly says this is not your usage limit and does not count against your quota.
- Server is temporarily limiting requests: a short-lived server throttle unrelated to your plan quota. Wait briefly before trying again.
- Session or weekly limit: further requests are blocked until the displayed reset time. These limits are shared across models.
- Request rejected (429): check the rate limit associated with your API key or cloud project, and confirm the active credential.
That distinction determines the next step. If the message names an exhausted allowance, follow the usage-limit guide. If it names capacity, begin with the service status and retry guidance in the error reference.
What does the Codex incident establish?
The official vendor status page records a resolved incident on 16 June 2026 titled “Codex ‘Selected Model is at Capacity’ Error,” classified as degraded performance. This establishes that the message has appeared as a service-side incident, rather than being only an anecdotal report.
The incident says affected services recovered. It does not explain how failed requests count toward usage. Do not transfer Claude Code's explicit quota statement to Codex, or treat this historical incident as evidence of a current outage. For a new occurrence, record the message and time before checking current service status.
How should you retry without losing the thread?
Claude Code already retries applicable transient failures with increasing delays before displaying an error. For repeated 529 overload, its reference recommends waiting a few minutes and checking the provider status page named in the message. It also suggests another model because capacity is tracked per model; this does not restore access after a shared session or weekly limit.
Set a stopping point for manual retries. Our retry-budget guide offers a way to keep attempts deliberate. Before resuming, record the goal, completed changes, checks already run, and next unfinished step. Ask for a review of that checkpoint before repeating an action that changes something outside the conversation.
For a persistent 429, the Claude Code reference recommends checking active limits and reducing concurrency. Avoid treating every error as a reason to resend the entire job immediately.
Where Octuo fits
Give Octuo a goal. It delegates work to supported tools and agents, carries the context they need and brings the results back. Octuo coordinates work through your own authorized accounts under each service's terms. It cannot change a vendor's capacity or limits.
When a supported tool is unavailable and you have authorized another, Octuo can hand the task on with the context. Octuo follows the work and reports back. Progress is there whenever you want to check; decisions that need you come to Attention.
New accounts get 1,000 OC trial credits, once per person, no card. OC stands for Octuo Credits.
FAQ
Does Claude Code's 529 mean I used everything?
No. Its error reference explicitly separates 529 overload from your usage limit and says it does not count against your quota.
Does the Codex incident explain usage counting?
No. It documents a capacity-message incident and recovery, without establishing how usage is counted for failed requests.
Should I keep resending while Claude Code retries?
Let the documented retry sequence run, then follow the specific error's recovery instructions. Keep a checkpoint and a limit on manual attempts.
Sources
The product names above belong to their owners. We have no affiliation with them.