Skip to content
NewMinniCode is out now, in Experimental Beta.Get MinniCode→
Minni AI
DemoEvidenceService
Products
Products
  • MinniMemoryMCPFlagship, early accessMemory for your AI agentSplits your agent’s memory into a small always-on part and files that load only when a task needs them.
  • MinniCodeExperimental BetaOpen-LLM optimized, low token coding agentA low token terminal coding agent, optimized for open LLMs. Reads, edits, tests and opens pull requests.
  • MinniTunerExperimental Beta, WindowsHardware optimization agentTunes how your PC uses its CPU, GPU and RAM. One plan you approve, every change undoable.
DocsMinniMemoryMCP docsInstall it, the commands, undoMinniCode docsInstall it, pick a model, the commandsMinniTuner docsThe tiers, Ask Minni, what is sent
See it workDemoThe full tour in one videoHow it worksEach product, step by step
Resources
LearnGuidesFAQnpm package
CompanyContactSupportPrivacyTermsData handlingSecurity

Guides

Claude Code usage limit reached: what to do, and how to hit it less

When Claude Code says you have hit your session limit or your weekly limit, you have used up a usage window on your plan, and switching models does not bring it back. The message shows when the window resets. Until then you can wait, turn on usage credits, or let Claude Code continue the task after the reset. To hit the limit less often, send less with every turn: each request carries the whole session again, and all of it counts.

Updated 2026-11-16

Which limit did you hit?#

The wording of the message tells you which ceiling you reached. They are not the same thing, and the fix is different for each. This table follows Anthropic’s cost docs.

The message saysWhat it meansWhat helps
You’ve hit your session limit, or your weekly limitA usage window on your subscription plan is used up. It is shared across all models.Wait for the reset time in the message, or use usage credits. Switching models does not help.
You’ve hit your Opus limit, or your Sonnet limitThe limit for that one model family is used up.Switch to a model outside that family with /model and keep working.
You’ve hit your spend limitYou are on usage credits, and they have reached a spend limit you or your admin set.Raise the limit, or wait for the plan reset the message names.
A context or auto-compact warningNot a usage limit. The conversation is close to the size where Claude Code summarizes older history.Run /compact, or /clear if you do not need the history.

On Team and Enterprise plans, Anthropic describes each seat’s allowance as a rolling five-hour window and a weekly window, shared with Claude chat and Cowork. So work you do in the Claude apps draws from the same allowance as Claude Code.

What to do right now#

  1. Run /usage. On a subscription plan it shows your plan usage bars, so you can see which window is full and when it resets.
  2. If you need to keep working, run /usage-credits. Usage credits let you continue past the plan limit and are billed on top of your plan. On a team plan without billing access, the command sends a request to your admin.
  3. If the work can wait, let it. Recent versions of Claude Code can wait for the reset and then continue the interrupted task on their own; /rate-limit-options shows the choice.
  4. If the message names one model, switch with /model. That only works for the model-specific message, not for the session or weekly one.

Starting a new session does not restore a plan window. It does help the next window last longer, which is the rest of this guide.

Why the limit goes faster than you expect#

Claude Code sends your full conversation with every request, and each time Claude uses tools it sends another request with those results attached. A one-line question late in a long session still draws usage for the whole conversation behind it.

We asked the same 30 questions in Claude Code 2.1.325 on Claude Sonnet 5.5, three full sessions a side: once with a test memory in the layout Claude Code itself writes, as it was, and once after MinniMemoryMCP 1.6.0 sorted it, with its server and hook on. In the sessions before any change, the tokens split like this:

Token kindTokensShare of all tokens
Fresh input490under 1%
Cache write134,0413%
Cache read4,133,08496%
Output46,5201%

Almost none of it was new text. Most of it was the same session being read back, turn after turn. Anthropic lists the usual reasons a long session climbs:

  • Long context. Everything still in the conversation is sent again on every request.
  • Cache misses. The first message after a long break misses the prompt cache and processes the whole context again.
  • Scheduled tasks and loops. They fire on their interval even while you are away, and each run sends the full context.
  • Subagents and agent teams. Each one sends its own requests on top of the main conversation.
  • Compaction. /compact has to read the conversation it summarizes, so compacting a big session is itself a big request.

How to hit the limit less often#

1. Read the breakdown in /usage#

On a subscription plan, /usage shows what your recent usage went to: skills, subagents, plugins and each MCP server. Under it are recommendations, one per row, such as trimming a named CLAUDE.md or lowering the effort level. Press d or w to switch between the last day and the last week. This is the fastest way to find your own biggest cost.

2. Clear between tasks#

Use /clear when you move to unrelated work. Old context is paid for again on every message that follows. Run /rename first if you want to return to the session with /resume.

3. Shrink what loads every turn#

Your CLAUDE.md files and everything they import load at the start of every session and stay in context for every turn. Anthropic suggests keeping CLAUDE.md under 200 lines and moving instructions for specific workflows into skills, which load only when used.

4. Match the model and effort to the job#

Routine edits run fine on a smaller model. Switch with /model, and lower thinking effort with /effort for simple work. Thinking is billed as output, the most expensive kind of token.

5. Turn off what you are not using#

Run /context to see what fills the window and /mcp to disable servers you are not using. Stop loops and scheduled tasks you no longer need.

The longer list, with the reasons behind each item, is in How to reduce Claude Code token usage. If you use Codex as well, see Codex usage limits.

Doing the memory part automatically#

Step 3 pays on every turn, and it is the one people put off, because splitting a memory file by hand takes time and has to be redone as the file grows. MinniMemoryMCP does the split for you. It sorts your CLAUDE.md or AGENTS.md, MEMORY.md and the files they import into a small part that loads on every turn and files Claude opens only when a task needs them. Every line is kept, and undo puts the originals back.

install it for Claude Code
$ npm i -g minnimemory
$ minnimemory install

With MinniMemoryMCP 1.6.0 on our test memory, the agent went looking in its memory 17 times instead of 89 over the same 87 answers, and the run used 47.2% fewer tokens. Measured 15 November 2026: at API rates, a Claude Code session on our test memory cost $0.47 before MinniMemoryMCP 1.6.0 and $0.29 after on average, 37.7% less (each of the three sessions 33.9% to 40.0% less). A blind judge found 80 of 87 answers correct before and 81 after.

The run counts cost and tokens. Fewer tokens on each turn means each turn draws less from your window; how much longer your window lasts depends on your own work. The method is on the Evidence page.

Try MinniMemoryMCP

Free, runs on your computer, and every change can be undone. Two commands install it for Claude Code; the docs cover Codex and the rest.

install it for Claude Code
$ npm i -g minnimemory
$ minnimemory install

More guides

  • How to reduce Claude Code token usage

    Where the tokens go each turn, and eight ways to spend fewer.

    Updated 2026-11-16 · Minni AI

  • CLAUDE.md too long: what Claude Code does with it, and how to split it

    What a long CLAUDE.md costs, the real size limits, and four ways to cut it.

    Updated 2026-11-16 · Minni AI

  • Claude Code context window keeps filling up: why it compacts, and what to do

    What fills the window, what compaction keeps, and how to compact less often.

    Updated 2026-11-16 · Minni AI

  • How to reduce Codex token usage

    Where Codex spends tokens, and seven ways to spend fewer.

    Updated 2026-11-16 · Minni AI

  • Codex usage limits: why they drain and how to use fewer tokens

    How the windows work, how to check what is left, and what uses the allowance up.

    Updated 2026-11-11 · Minni AI

  • AGENTS.md too large: what Codex cuts off and how to split it

    The 32 KiB cap, how to see which files load, and five ways back under it.

    Updated 2026-11-11 · Minni AI

  • How to lower a Claude Code or Codex API bill

    What a coding agent bills on an API key, and the levers that move it.

    Updated 2026-11-16 · Minni AI

  • Why Claude Code sessions get expensive

    Every turn re-sends the whole session. What makes that grow.

    Updated 2026-11-05 · Minni AI

  • Claude Code memory: CLAUDE.md vs MinniMemoryMCP

    What belongs in CLAUDE.md, and splitting the rest out by hand or with a tool.

    Updated 2026-11-16 · Minni AI

  • MinniMemoryMCP vs Mem0, Zep, supermemory and Letta

    Four tools add memory to an agent. MinniMemoryMCP cuts what the agent already loads. When each fits.

    Updated 2026-11-16 · Minni AI

  • How Claude Code remembers across sessions

    What carries over between sessions, what does not, and how to keep it small.

    Updated 2026-11-16 · Minni AI

  • Where Claude Code keeps its memory

    Every memory path on your machine, what each file is for, and which ones load every turn.

    Updated 2026-11-07 · Minni AI

  • How to run a coding agent on free, open models

    What a free key gets you, what a local model can do, and where the tokens go.

    Updated 2026-10-25 · Minni AI

  • Get a free NVIDIA API key for a coding agent

    Where the key comes from, where to keep it, and how to run a coding agent on it.

    Updated 2026-11-07 · Minni AI

  • What a Windows PC optimization agent should and should not touch

    The settings worth changing, the ones that are placebo, and the ones that break things.

    Updated 2026-10-25 · Minni AI

GuidesMinniMemoryMCPHome
© 2026 Minni AI. All rights reserved.