You Hit Your Claude Limit. Now What?

It happens mid-task. You’re deep in a run — a draft half-built, a coding session finally in rhythm — and the message lands: you’ve hit your usage limit. In Claude Code the banner is plainer about it: “Usage limit reached · wrapping up.” The work isn’t done. The deadline doesn’t care.

This happens in our shop often enough that we stopped treating it as an emergency and started treating it as weather. You can’t stop it from raining. You can own a roof. This page is the roof: what the wall actually is, what to do in the first fifteen minutes, the structural fixes that keep a limit from stranding work, and how to think about the money when it keeps happening.

What the wall actually is

Three different walls get called “the limit,” and which one you hit decides what to do next.

The five-hour session window. Paid plans run on a session limit: a five-hour window that starts with your first message and resets in full five hours later. It isn’t a rolling drip that refills as you go. It’s a shift. When the shift ends, you’re back — which means a session wall is a scheduling problem, not a crisis.

The weekly cap. Paid plans also carry weekly limits, and those reset at a fixed time each week that Anthropic assigns to your account. Hit the weekly wall and no amount of waiting until tonight helps; your reset might be days away. This is the wall that actually hurts.

One pool, every surface. Your chats on the web, the desktop app, your phone, and Claude Code all draw from the same account limits. The heavy coding session you ran this morning is why the chat died this afternoon. Switching apps doesn’t dodge anything — it’s the same tank.

You can see both clocks in Settings > Usage: a “Current session” bar for the window, and your next weekly reset time printed next to it. Two minutes in that screen tells you which wall you’re looking at, and that’s the first thing to know before you do anything else.

There’s a fourth wall people confuse with these three: API rate limits. Those are a separate system entirely — set per organization and per model, not per person — and the confusion matters, because the API turns out to be one of the ways around the other three. More on that below.

If you want the full map — every plan, every price, every limit in one place — that’s our complete guide to Claude pricing, plans, and limits. And if what stopped you wasn’t a usage limit at all but a file or image error, the exact error strings and caps are collected in our guide to Claude usage limits, file caps, and error messages. This page is the other half: not what the limits are, but what you do at the wall.

The first fifteen minutes

Minutes 0–2: stop, and read the wall. Don’t re-send the prompt. Don’t open a second chat and try there — same pool, same wall. Open Settings > Usage and see which limit you hit and when it resets. That one fact picks your whole next move.

If it hit mid-response in Claude Code, land the plane. Claude Code has a small wrap-up allowance: if the session limit lands while it’s mid-step, it may briefly finish the step in progress before stopping. It’s capped, it counts toward your weekly limit, and it’s not generous — on Pro it can happen once per weekly period; on Max, each time the session limit is reached. Use that grace to get the work to a clean stopping point. Do not use it to start something new.

Get the work out of the chat and into writing. Whatever the job is, produce the state of it: what’s done, what’s next, which decisions are still open, which files were touched. In this shop that’s a handoff note, and it’s the same discipline behind how we run this business on written work orders. A limit strands work only when the context lives in one model’s head. The moment it’s written down, any seat — another model, another provider, you tomorrow morning — can pick it up cold.

Then pick one of three doors. Park it: the reset is soon and the work can wait — fine, write the note and walk away. Move it: the work can’t wait, so it goes to a different seat or the API (below). Pay through it: turn on usage credits and keep going on the same account (also below). Every bad limit story we’ve lived came from picking none of the three and just pushing on the door.

The structural fixes a working shop uses

These are ours. They’re practice, not policy — but they’re the difference between hitting the wall monthly and hitting it never-quite-the-same-way twice.

Spread the work across seats. We run more than one AI seat, with lanes: different models, and not all of them on one provider’s meter. When one pool runs dry mid-job, the job moves — because the handoff note exists, the move costs minutes, not a restart. A one-model shop has a single point of failure with a five-hour reset.

Route bulk work to cheaper seats and the API. Summaries, sorting, extraction, first-pass drafts — high-volume work doesn’t need your flagship model or your chat plan’s pool. API usage is billed separately from your plan limits, and a small fast model on the API costs a fraction of what the big one does. Save the plan pool for the work that actually needs you in the conversation.

Treat your first message like a shift start. Because the five-hour window opens with your first message, the clock is a tool. If you know a heavy run lands at 2 p.m., don’t open the day at 8 a.m. with trivia and arrive at the real work with half the tank gone. Know when your window started; plan the heavy lifts inside it.

Batch, and keep threads lean. Anthropic’s own best-practice guidance lines up with what we’ve learned the expensive way: batch related requests into one message instead of dribbling them out, plan the conversation before you start it, use Projects for work you’ll return to, and watch the Usage screen instead of guessing. And when a conversation gets long, start a fresh one with a short summary rather than dragging the whole history forward — long threads cost more of your limit with every turn.

Make the handoff a habit, not a rescue. Every job here ends in writing: done, next, open questions. It reads like paperwork until the day the wall hits mid-job — then it’s the whole business, still moving.

The money question: credits, upgrade, or API?

Three levers, in order of commitment.

Usage credits are the pay-as-you-go lever. On Pro, Max, and Ultra you can turn on usage credits in Settings > Usage. Past your limit, work continues at standard API rates until you hit the spend limit you set; the notice changes to “Now using credits,” so there’s no surprise about which meter is running. Two fine-print items worth knowing before you lean on them: credits are non-refundable, and credits bought on or after December 7, 2026 expire twelve months after purchase. Credits fit the occasional overrun — deadline week, the one big push. Turn them on before the week you need them.

Upgrading is the flat-rate lever. If you’re at the wall every week, credits are a taxi meter running all month. Max is $100 a month and gives you five times Pro’s usage — every five hours and every week. Ultra is $200: ten times Pro’s weekly usage and, for verified accounts, no five-hour limit at all. Upgrades apply right away, so you can make the call mid-crisis and have the headroom in the same session. We worked through the upgrade math in detail in Claude Pro vs Max: is the $100 upgrade worth it? — the short version: count your wall-days per month; if they’re routine, the flat rate wins.

The API is the structural lever. API use runs on its own billing and its own limits, separate from your plan. Work that is automated, heavy, or runs while you sleep often belongs there from the start rather than as an escape hatch. One wrinkle worth checking before you pay for anything: Max and Ultra now include monthly API credits — $100 a month on Max, $200 on Ultra — claimable by linking a Console organization in Settings > Billing. Our Anthropic Console guide walks through that side of the account. But keep the buckets straight, because they are genuinely separate: those monthly API credits do not cover interactive Claude Code or extra usage inside the apps, and usage credits are a different bucket again. Mixing them up is an easy way to pay twice for the same wall.

On a Team plan the same logic runs per seat — Standard and Premium seats carry different limits, and which seats hit walls first is a rostering question. The numbers are in our Claude Team Plan usage limits guide.

What not to do

Don’t burn the window on retries. Near the wall, every re-send of a long thread costs more of what’s left, and the reset time doesn’t move because you asked harder. On the API side the same rule is mechanical: a rate-limit error tells you how long to wait, and retrying earlier just fails again. Wait it out or route around — those are the only two moves.

Don’t open duplicate accounts to dodge the limits. The limits exist so the service stays usable for everyone; accounts opened to get around them are a violation waiting for enforcement, and the day an account closes, everything in it — projects, history, context — goes with it. Even setting the rules aside, it’s fragile operations: a shop whose workflow depends on a workaround has built on sand.

Don’t confuse the buckets. Plan limits, usage credits, and monthly API credits are three separate things with three separate rules. Most “I paid and still hit the wall” stories are a bucket mix-up, not a billing error.

The short version

The wall isn’t the problem. Hitting it with no plan is. Know which wall you hit, write the handoff before you need it, keep a second route warm for the work, and decide the money question — credits for the rare overrun, a bigger plan for the weekly habit, the API for the heavy machinery — while you’re calm, not mid-deadline. The limit will still show up. It just stops being an emergency.