What to do after repeated Claude Code 529 errors
Handle Claude Code's “Repeated 529 Overloaded errors” message without damaging the session: check status, retry later, or switch to an available model.
“Repeated 529 Overloaded errors” means Claude Code exhausted its retries while the API reported overload. Preserve the session, check Anthropic's status page, and retry after a pause. If another model is available to your account, use /model or start with --fallback-model; reinstalling Claude Code does not repair server capacity.
What the message means
HTTP 529 is a capacity response from the service side. Claude Code retries transient failures, so the word “Repeated” means several attempts already failed. Your repository and saved conversation are not the cause, although a proxy or gateway can produce a different upstream failure that should be diagnosed separately.
Fix it in this order
1. Check whether the service is degraded
Open the official status page and compare its incident time with your failed turn. A broad incident calls for waiting, not local cleanup. Keep the terminal output if you later need to report the time and request identifier.
open https://status.claude.com/2. Retry without duplicating side effects
Before resending, inspect the working tree and any external action the interrupted turn could have completed. A streamed answer may fail after a command ran. Retry the remaining work, not blindly the whole instruction.
git status --short
git diff --stat3. Use an available fallback
In an interactive session, /model can select another model. For a fresh launch, --fallback-model accepts models Claude Code may try when the primary is overloaded or unavailable. Availability still depends on your account.
claude --fallback-model sonnetImportant distinctions
- A 529 is not evidence that your prompt is too long or that your local installation is corrupt.
- Fast repeated retries can add noise without restoring capacity; wait long enough to distinguish an incident from a single transient response.
- If only a company gateway fails while Anthropic reports healthy service, give the gateway administrator the timestamp and sanitized error details.
Where Crowsnest fits
Because the native Claude Code transcript stays local, Crowsnest can reopen the conversation after capacity returns. It does not proxy the request or make an overloaded Anthropic endpoint available.
Source and version
The exact text and flags on this page were checked against the installed Claude Code 2.1.286 binary on October 9, 2026. Version-specific behavior can change, so compare your own --help output before scripting around it. Official status or documentation →
Reviewed from first-party CLI output and the released Crowsnest product source. No command on this page bypasses provider limits, billing, authentication, or native history rules.