What to do when Claude Code hits its usage limit

The message arrives in the middle of something. The session stops. You have a choice between waiting an unknown number of hours and paying for a second plan, and neither one is what you wanted to be deciding.

A limit is a window, not a wall

The important thing about a usage limit is that it ends. You are inside a rolling window, and when that window rolls forward the account works again. Nothing was lost and nothing was broken. Your access was scheduled, and the schedule says not yet.

This reframes the whole problem. If a limit were a wall you would need more capacity. Because it is a window, what you actually need is better scheduling.

That distinction is the difference between buying a third subscription and using the two you have properly.

Retrying is the worst available option

The instinct when a session stops is to try again. Sometimes it appears to work, which is the trap, because what happened is that the window rolled over between your attempts and not that the retry did anything.

Retrying in a loop has three costs and no benefit. It burns your attention on a thing that has a known answer. It makes the moment the account comes back a coin flip rather than something you planned around. And it trains you to sit and watch a terminal, which is exactly the posture these tools were supposed to get you out of.

The account will come back on its own schedule whether you are watching or not.

Ask before you spend

The better habit is to ask what an account has left before you give it a large job, rather than discovering the answer halfway through.

Every one of these tools can report how much of its window is left and roughly when it resets. Asking costs nothing and does not interrupt a session that is already running. Done before a round of work rather than during one, it turns a limit from an interruption into a fact you planned around.

Two things worth knowing about the numbers:

• Reset times are sometimes estimates. When a tool has to guess, an honest interface says it is guessing. A guess that looks like a fact is worse than no number at all.
• The account doing the planning spends quota too. If you have one account coordinating others, that coordination is real usage on a real plan. Budget for it.

Spread the work instead of queuing it

If you have more than one account, a limit on one of them is not a limit on you. The work that account was going to do can go to another account that still has room.

This is the part that is tedious by hand. You have to know which accounts have capacity, split the job so two agents are not editing the same files, start each one in a place where it will not collide with the others, and then bring the results back together. That is real work, and it is the reason most people with three subscriptions still run one at a time.

Done automatically it looks like this:

1. 01You give one goal to the pane you put in charge.
2. 02That pane reads the project and turns the goal into a task per account, sized so no two agents touch the same files.
3. 03The tasks run at the same time, each in its own workspace. An account that is out of quota holds its task rather than dropping it.
4. 04When that account's window comes back, its task starts itself. No one had to be watching.
5. 05Everything arrives on one branch for you to read.

Waiting out a usage limit counts as waiting, not as failing. A run that pauses for three hours and then finishes is a run that finished.

The setup that makes this work

Three things have to be true before parallel accounts help at all.

Each account needs to stay signed in while the others are. Each agent needs its own working copy so simultaneous edits do not collide. And you need to see the state of every account in one place, or you will not use the second one.

Nuvoa does those three things on macOS: a pane per account, each with its own sign-in and its own branch, and a sidebar showing what every account has left. Held work restarts itself when a window comes back.

If you have hit a limit today and you have another account sitting idle, that is the problem worth fixing. Join the waitlist.