Your Claude Code 5-hour limit ran out in minutes and you did nothing different. On Oct 27, 2026 a post on r/ClaudeAI with over 1,500 points reported exactly that: the author measured 1.306 billion tokens for the day with ccusage, against an average of 161 million on previous days, cache reads included. The cause is not confirmed. What you control is measuring what is consuming and cutting what weighs most.
Is Anthropic to blame for the Claude Code limit draining?
We cannot say yet. There was an official incident the same day (elevated errors on Sonnet 5.5, which we covered in another article), but I found no official source linking the incident to limit consumption.
The Reddit author says support replied that retries caused by service errors count toward the limit. That is one user's account, with no public confirmation from Anthropic. What the official errors documentation does say is different: Claude Code retries transient failures up to 10 times with exponential backoff, and a 529 overloaded error does not count against your quota.
So the honest path is the same in both scenarios: find out whether the spend comes from your own usage, and reduce what is yours.
How do you see what is consuming the limit with /usage?
Run /usage inside Claude Code. On Pro, Max, Team and Enterprise plans, the screen shows the plan bars and a breakdown of what counts against your limits: the share attributed to skills, subagents, plugins and each MCP server, plus recommendations with the share of usage each one affects.
/usage- Press
dorwto switch between the last 24 hours and the last 7 days. - A row such as
25% Trim ~/code/api/CLAUDE.md · 49k tokens per requestsays your CLAUDE.md weighs on 25% of recent usage. - When the footer shows
f to fix, thefkey applies the recommendations Claude Code can act on (needs a recent Claude Code version). - The figures are approximate and come from local history on this machine. Usage on another computer or on claude.ai is not included.
The Session block at the top shows tokens and dollars for the current session. On a Pro or Max subscription the dollar figure is not a charge, it is an estimate at list price.
How do you compare against your history with ccusage?
ccusage reads local history and sums tokens per day, session or 5-hour window. It is the tool the post author used to find the spike. No install needed:
npx ccusage@latest daily
npx ccusage@latest blocks
npx ccusage@latest session
npx ccusage@latest daily --since 2026-10-20 --breakdowndailyshows tokens per day. Compare today with the weekly average.blocksshows Claude Code's 5-hour windows.sessionshows which session weighed most.--breakdownsplits by model and--sincefilters the period.
One catch: the ccusage total includes cache reads, which are cheap. The Reddit post says so itself: the numbers alone do not prove the cause. Also look at output tokens, which barely move when the problem is just a large context.
What usually drains the limit without you noticing?
The official Claude Code cost documentation lists the most common causes of high usage in long sessions. The table maps each one to where to see it and what to do.
| Cause | How to see it | What to do |
|---|---|---|
| Long context: every request resends the whole conversation | /context | /clear when switching tasks, /compact mid-task |
| Cold cache: the first message after a pause reprocesses everything | Prompt cache line in /usage | Avoid old sessions left open; start clean |
| Heavy model: Opus uses more quota than Sonnet, and Sonnet more than Haiku | /model | Sonnet day to day, Opus only for the hard part |
| High extended thinking | recommendation in /usage | Lower /effort on simple tasks |
| Large CLAUDE.md, loaded every turn | recommendation in /usage | Under 200 lines; move the rest to skills |
| MCP, subagents and scheduled tasks | attribution in /usage | /mcp to disable what you do not use |
Which commands cut spend right away?
In order of impact, per the official documentation, which calls /clear the most effective lever:
/rename my-task # name it before clearing
/clear # start fresh when changing topic
/resume # go back to the named session if needed
/compact Focus on code samples and API usage # summarize, keep what matters
/model # switch to Sonnet for ordinary tasks
/effort # lower effort on simple tasks
/mcp # disable MCP servers you are not usingTwo cautions. /compact also reads the whole conversation to summarize it, so compacting a huge context is itself a big request. And on Opus 5.5, Sonnet 5.5 and Haiku 5.5 thinking cannot be turned off, only reduced through the effort level.
Two more practices from the documentation: reference file paths instead of pasting content (pasted content stays in context to the end of the session) and ask for a plan before large changes, using Shift+Tab to enter plan mode.
What if the limit still runs out anyway?
Then the problem may not be your usage. Record the date, run npx ccusage@latest daily and keep the output before opening a support request, because that is what the Reddit author used as evidence. To keep working meanwhile, the session limit message shows when the window resets, and /usage-credits opens usage credit management for subscribers.
All this measuring and trimming of context exists because the limit is the yardstick. On Verboo Code tokens are unlimited, so the long session that costs quota today costs the same as the short one, and what is left to look after is the quality of the context, not the balance.
