← All guides

Claude Code hit the rate limit or quota? Here's how to keep working

If Claude Code stops mid-task with a usage-limit or rate-limit message, you've hit either a per-minute rate cap or your plan's usage quota. Here's how to tell which, and how to keep going.

TL;DR: A '429 / rate limit' means too many requests too fast — wait a bit and it clears. A 'usage limit / quota reached' means you've spent your plan's allotment for the window and it resets on a schedule. To stop getting interrupted, either upgrade, wait for the reset, or point Claude Code at your own API key / a different model so you're not bound to one plan's cap.

First: which limit did you hit?

MessageWhat it meansWhat to do
429 / rate limitToo many requests in a short windowWait 30–60s and retry; it clears on its own
Usage limit / quota reachedYou've spent your plan's allotment for this periodWait for the reset, upgrade, or use your own key
Overloaded / 529The service itself is busyRetry shortly; it's not your account

Keep working right now

Wait for the reset

Quotas reset on a rolling schedule. If you're close to the window, a short wait gets you going again.

Slow down the request rate

For a plain 429, batching or pausing between big actions avoids tripping the per-minute cap.

Switch to your own API key

Running against your own key (billed as usage) isn't bound to the subscription's session quota, so you don't get cut off mid-task.

Stop it interrupting you again

The frustrating part isn't the limit itself — it's getting cut off in the middle of a task with no fallback. The durable fix is to not be locked to a single plan's quota. If your client can bring your own key, or switch to another model/provider when one is capped, you keep momentum instead of waiting for a reset. Some setups let you keep a cheaper model on standby and only reach for the expensive one when you need it.

A rate limit (429) clears in seconds to a minute. A usage/quota limit lasts until the reset window. Knowing which one you hit tells you whether to wait a minute or change your setup.

The bigger picture

Being at the mercy of one plan's usage cap is a workflow risk when you're on a deadline. A client that lets you bring your own key, or fall back to a second provider when the first is capped, means a quota never fully stops you — you just switch and keep going.

FAQ

How long until my Claude Code usage limit resets?

Usage quotas reset on a rolling window tied to your plan. A plain rate limit (429) clears within seconds to about a minute; a usage/quota limit lasts until the next reset.

Is there a way to not get cut off mid-task?

Yes — don't be bound to a single plan's session quota. Running against your own API key (billed as usage) or being able to switch models/providers means a cap on one doesn't stop your work.

What's the difference between a rate limit and a usage limit?

A rate limit (429) is about requests-per-minute and clears quickly. A usage limit / quota is about total spend in a period and lasts until the reset window.

Tired of a single plan's quota stopping you mid-task? Wuwei is a free, open-source AI agent that lets you bring your own key and switch models/providers freely — so hitting one cap never fully blocks you. Keep working, just switch and go.

Windows · macOS · Linux — free, no login