Bivy

Claude Code hit its usage limit: what you can do

Checked 16 November 2026

On a Pro, Max, Ultra, Team or Enterprise plan, Claude Code draws from a usage allowance with a weekly limit and, on most plans, a five-hour session limit. When one runs out, Claude Code stops sending requests until the reset time in the message. You can wait, pay for more, switch to an API key, switch model if the limit is model-specific, or move the task to another agent.

The short answer: read the message first. A session or weekly limit applies to every model; an Opus or Sonnet limit applies to one family. If the reset is soon, keep the session open and let Claude Code continue after it. If you need to keep going now, turn on usage credits or use an API key, both billed at API rates. If you have another agent's plan, commit your work, write a short summary and continue there.

This page is published by Bivy, which is one of the options below. Each claim about Claude Code comes from Anthropic's own docs and help center, and each claim about another tool from that tool's docs, linked under Sources. Limits and commands change often, so check the linked page before you rely on a detail.

How the limits work

What the message means

Messages as listed in Anthropic's Claude Code error reference on 16 November 2026.
MessageWhat ran outDoes /model help?
You've hit your session limit · resets 3:45pmThe five-hour session allowance, across all modelsNo
You've hit your weekly limit · resets Mon 12:00amThe weekly allowance, across all modelsNo
You've hit your Opus limit or Sonnet limitThe allowance for that model familyYes, switch to a model outside that family
You've hit your monthly spend limit and similarUsage credits reached a spend cap you or your admin setNo; raise the cap or wait
Credit balance is too lowPrepaid Console API credits, or Claude Code is using an API key you didn't mean to useNo; see the API key section

See where you stand

Run /usage in Claude Code. On a subscription it shows plan usage bars, when each limit resets, and a breakdown of what used your allowance, such as skills, subagents, MCP servers and loops, with suggested changes. The breakdown is computed from this machine's history only. Settings > Usage on claude.ai shows the current session and weekly bars and when each resets. Claude Code also warns you before a window runs out, for example You've used 85% of your session limit.

Wait for the reset

The free option, and often the right one for a session limit. Claude Code blocks requests until the time in the message.

Buy usage credits

Keep using your subscription past the limit and pay for the extra. Anthropic calls these usage credits. They are available on Pro, Max and Ultra, and on Team and Enterprise if your admin turns them on.

Use an Anthropic API key instead

Bill Claude Code per token through the Claude Console instead of your plan. Anthropic's help center suggests this for intensive coding sprints.

Switch model

Helps only with an Opus or Sonnet limit. Run /model and pick a model outside the family that ran out. Each model has its own prompt cache, so the next request re-reads the whole conversation.

To make the allowance last longer next time, Anthropic's docs suggest Sonnet for most coding, /clear between unrelated tasks, a shorter CLAUDE.md, and the recommendations in /usage.

Move the task to another agent

Use a plan you already pay for with another vendor. Your repository and files stay where they are; what you have to carry over is the conversation.

Carry the context over by hand

  1. Save the code state. Commit or stash what Claude Code changed, or at least note git status and the branch. The next agent reads the files, not the old conversation.
  2. Write a handoff summary. If you see the 85% warning, ask Claude Code for a short summary: the goal, what's done, what's left, decisions made, and commands that test the work. Save it to a file in the repo. After the limit, write it yourself.
  3. Share project instructions. Codex and OpenCode read AGENTS.md. OpenCode falls back to CLAUDE.md when there's no AGENTS.md. Gemini CLI reads GEMINI.md by default and can be set to read AGENTS.md with context.fileName. Claude Code reads AGENTS.md when a repository has no CLAUDE.md, or through an @AGENTS.md import, so one shared file can serve all of them.
  4. Start the other agent in the same directory and point it at the summary file.

Expect some loss. A summary doesn't carry every detail, tool result or rejected idea from the original conversation.

Bivy

An open-source (MIT) workspace that runs coding agents on your own machine or a Bivy cloud computer, and steers them from a phone, browser or terminal. Two of its features apply here. Its README says: "Hit a usage limit? Keep going. Fork the session, code and conversation included, to another agent, or let Bivy pick it up again when the limit resets."

Which should you pick?

FAQ

When does my Claude Code usage limit reset?

The limit message shows the reset time, for example "You've hit your session limit · resets 3:45pm". Pro and Max plans have a five-hour session limit and a weekly limit. Run /usage in Claude Code, or open Settings > Usage on claude.ai, to see both and when they reset.

Does switching models get around the limit?

Only for a model-specific limit. Anthropic's docs say the session and weekly limits are shared across all models, so /model doesn't help. After "You've hit your Opus limit" or "You've hit your Sonnet limit", switching to a model outside that family keeps you working.

Can I keep using Claude Code after hitting the limit?

Yes, if you pay for it. On Pro, Max and Ultra you can turn on usage credits, billed at standard API rates, with /usage-credits. Or sign in with a Claude Console account or set ANTHROPIC_API_KEY, and Claude Code bills per token instead of drawing on your plan.

Does Claude Code continue on its own after the reset?

In an interactive session signed in with a claude.ai subscription, Claude Code v2.1.234 or later waits and continues the task after the reset, as long as you keep the session open. It doesn't start the wait on its own for a reset more than 24 hours away, such as a weekly limit.

How do I move the task to another agent without losing context?

Commit or note your git state, ask Claude Code for a written summary before you run out if you can, and keep project instructions in AGENTS.md, which Codex and OpenCode read. Then start the other agent in the same repository and give it the summary.

Sources

All checked on 16 November 2026.

Want to try Bivy? Start on a cloud computer with nothing installed, or connect your own Mac or Linux machine.

Start free on Bivy Cloud

Browse setup and security resources →