When Claude Code says “limit reached,” first identify the limit: subscription, API rate limit, spending cap, or account issue. The right remedy may be to wait for a reset, enable official usage credits, reduce concurrent calls, or fix a key. Buying another plan before making this diagnosis may leave the problem unresolved.
What message are you seeing?
| Symptom | Check | Appropriate action |
|---|---|---|
| Plan quota reached, with a reset time shown | Claude account and usage page | Wait, compare another plan, or check usage credits |
| API 429 indicating a rate limit | Message, concurrent requests, and reset header | Slow down and follow the stated delay |
| Spending cap or payment declined | Balance, account limits, and billing | Correct the relevant limit or payment |
| API 401 or 403 | Key, destination domain, and permissions | Correct authentication or authorization |
| Conversation too long | Context size and exact message | Summarize the work and reduce the relevant context |
The codes below describe the Anthropic API. If Claude Code goes through another provider, also check that provider's documentation: an intermediary may show its own messages and limits.
1. If you are using a Claude subscription
Open the usage settings for the connected account. Check which quota has been reached and the time shown, rather than inferring a universal duration from a message found elsewhere. Also verify that Claude Code is using the intended account.
Anthropic distinguishes usage limits and length limits. Claude and Claude Code usage may draw from the same account allocation. Opening a new window or conversation therefore does not create additional quota. However, trimming an oversized context can reduce the work the model has to do on subsequent calls.
To continue after using the included allocation, eligible personal plans offer official usage credits. They are billed separately at standard API rates. In usage settings, check that they are enabled, the available funds, and the spending cap. Compare this option with waiting, switching plans, or using a separate API account.
2. If the API returns 429
Check the error text and the API limits. For a rate limit, reduce concurrent tasks and follow the retry-after delay when provided. Immediately relaunching several agents can prolong the same blockage.
A 429 can also indicate the API tier's monthly cap or certain spending limits in the Claude Code workspace. A monthly cap may not provide a reset delay. In that case, check the account's billing and associated cap; retrying in a loop will not raise them. The absence of a header alone is not enough to draw a conclusion: read the message too.
3. If the issue concerns balance or authentication
The Anthropic error reference distinguishes, among other things, 401 for authentication, 403 for permissions, and 402 for billing. Some spending limits may also appear under a 400 code. The HTTP code alone does not replace the error details.
Check the destination domain receiving the request and the account that created the key. A Claude subscription, a Console balance, and a balance with a third-party provider are not interchangeable. Topping up with one provider does not automatically fund the others. After fixing the issue, use a small request to confirm which account is charged before resuming an important task.
4. Continue with separate API billing
The gateway documentation explains that an active gateway identifier replaces the subscription identity for the session. Setting only the base URL does not make this change: the saved login can remain active. Configure the expected URL, identifier, and model together.
The Claude Code pricing and setup guide explains the Kunavo option in French. The catalog currently lists Claude Sonnet 4.6 at $2.10 for input and $10.50 for output per million tokens. The Claude API pricing guide explains the units to compare. A task may involve several calls; its cost also depends on context, cache, and retries.
If this separation works for you, create your Kunavo account, configure a key, then check the first call in your usage history. This account has its own constraints; it does not make Claude Code an unlimited service.
Preparing a useful support request
If the issue persists, keep the following information. It helps distinguish a configuration problem from a limit applied to the correct account, without exposing your secret key:
Interface et version de Claude Code :
Compte utilisé : abonnement / Console / fournisseur tiers
Modèle et nom de domaine de l'API :
Message exact et code HTTP éventuel :
Heure de réinitialisation affichée :
En-tête retry-after, s'il existe :
Identifiant de requête, s'il existe :Also preserve your local work and task state. Once access is restored, ask the agent to check which files have already been modified before starting again, to avoid repeating completed steps or losing the context of your fix.
Frequently asked questions
What should I do when Claude Code says “limit reached”?
First identify the account providing the responses. For a subscription, check the reset time and usage-credit options. For an API, read the full message: rate limits, spending caps, billing, and authentication each require different fixes.
Does a 429 code always mean I should wait?
No. The Claude API also uses 429 for some spending limits. A rate-limit error may require waiting and reducing concurrent requests; a financial limit calls for checking the account's limits and billing. The message and headers help you choose the right course of action.
Does starting a new conversation reset my quota?
No. A new conversation can reduce the context sent, but it does not reset the account's allocation. A conversation-length limit and your subscription's usage limit are two different constraints.
Does a Kunavo key remove all limits?
No. An API setup with a Kunavo key uses an account and billing separate from your Claude subscription. It is still subject to Kunavo's balance, limits, and available models. Changing only the base URL without configuring the correct identifier is not enough to change the billing.
Official sources verified on September 17, 2026.