Why Your Claude Usage Runs Out So Fast (October 2026), and Ten Habits That Make It Last

"I sent twelve messages and I'm already at 60%" turns up in r/ClaudeAI almost every day. Claude doesn't count messages, though. It counts how much it has to read and write, so a short chat that drags a long history, a few files and three connectors behind it can cost more than a hundred quick questions.

I learned this the expensive way. I run Claude Code for a side project in one long session that never really closes, with around eighteen scheduled jobs: a message check every fifteen minutes, an hourly posting job, a few daily reports. On Sunday 18 October 2026 it ran out of its weekly allowance at about 2:30 in the afternoon and stayed locked until about 9 on Monday night, roughly 31 hours. Nothing was broken. Anthropic's own cost guide describes that exact setup as one of the main reasons usage climbs: every timer that fires re-sends the whole context.

So I went back through the official help pages and the Claude Code docs. What follows is what they say as of 19 October 2026, and what I changed afterwards.

How the limits work now

• Paid plans have a session limit that resets every five hours and weekly limits that reset once a week, at a time fixed to your account. You can see both, and the next reset, in Settings → Usage on claude.ai.
• claude.ai, Claude Code and Claude Desktop share the same allowance. A heavy coding afternoon leaves less for chat that evening, and the other way round.
• What you use depends on how long and complex the conversation is, the model, the features you switch on and the effort level, not on the number of messages.
• Max 5x and Max 20x give five and twenty times Pro's per-session allowance. Max also has a separate weekly limit for Fable.
• When you hit a limit you can wait, upgrade (new limits apply straight away) or turn on usage credits. Credits keep you going at standard API rates, which is where surprise bills come from. More on that below.

On 6 May 2026 Anthropic doubled Claude Code's five-hour limits on Pro, Max, Team and seat-based Enterprise plans, and removed the peak-hours reduction for Pro and Max. The announcement said nothing about weekly limits. That fits the many "my session lasts longer but my week runs out sooner" posts since then.

Related reading: How to Put a Hard Spending Cap on AI Agents (OpenAI, Claude, Bedrock, OpenRouter) Before an Overnight Run Costs You Thousands · How to Stop ChatGPT, Claude, Gemini and Copilot Training on Your Data (and Check It Stayed Off)

What actually eats your allowance

The whole conversation goes back every time. Each new message re-sends everything above it. Message 40 of a long chat costs far more than message 4, even if you only type "thanks". In Claude Code it's worse, because every tool call sends another request carrying the results.

Breaks cost more than you'd think. Repeated content is cached and counts for less, but the cache expires. Anthropic's best-practices page says your first message after a long break counts the full content again. In Claude Code the cache lasts an hour on a subscription, but drops to five minutes once you're drawing on usage credits.

Tools and connectors are expensive. The help center calls them "token-intensive". Web search, Research and every connected app add their own text to the conversation.

Model and effort. Opus uses your allowance much faster than Sonnet, and Sonnet faster than Haiku. Higher effort means more thinking, and thinking counts as output. On the 5.5 models and Fable you can't turn thinking off, but you can lower the effort level.

In Claude Code, things that run while you're away. The cost guide lists these:

• scheduled tasks and /loop jobs, which send your full context each time they fire;
• messages from your other sessions;
• goal check-ins;
• subagents, each with its own requests;
• agent teams. The guide says teams use roughly 7 times the tokens of a normal session when teammates run in plan mode.

Compacting a big conversation is itself a big request, and long chats that auto-compact keep using more of your limit than a fresh one.

Where to see what's using it

• claude.ai: Settings → Usage shows the session and weekly bars and when each resets.
• Claude Code: type /usage. On Pro and Max it also shows a breakdown of recent usage:
  • what share went to skills, subagents, plugins and each MCP server;
  • flags for any behaviour, like long context or cache misses, that takes 10% or more;
  • a row for each heavy loop or scheduled task, with how often it fires and tokens per run.
  • Press d or w to switch between the last day and the last week. The figures come from this machine only, so chats on claude.ai aren't in them.
• Usage credits: the same /usage screen shows your credit spend against your monthly limit. If it says "Unlimited", nothing stops a runaway session from billing you. Set a limit in Settings → Usage → Usage credits.

What I changed, and what else the docs suggest

The first thing I changed was the scheduled jobs. The message check was firing every fifteen minutes, but the script behind it only fetches new messages once an hour, so three runs out of four were re-sending my whole session for nothing. It now runs every thirty minutes. If /usage shows a loop near the top of the list, that's the first place to look. An idle session with a timer isn't idle.

The second was starting fresh far more often. A new chat per task on claude.ai, and /clear in Claude Code (/rename first if you'll want it back), means each message stops paying for an afternoon of old history. When I need continuity, a three-line summary at the top of a new chat is much cheaper than dragging 200 messages along.

Beyond that, the docs and help center list a handful of smaller savings:

• Sonnet covers most coding and writing. Haiku is enough for quick lookups and simple subagents, and Opus is for problems that genuinely need it.
• /effort, or the effort setting in the model menu, cuts thinking on easy tasks. On the 5.5 models you can't switch thinking off, so this is the only dial.
• Connectors and web search you aren't using still cost tokens. On claude.ai switch them off per chat; in Claude Code, /mcp lists servers to disable and /context shows what's filling the window.
• Documents you keep coming back to belong in a Project, where cached content counts for less than pasting the file again.
• Leaving a half-finished task over lunch means the cache expires and your next message re-reads everything.
• Anthropic's help center recommends deciding what you need first, then putting related questions and background into one message to cut the back-and-forth.
• Subagents can run on a smaller model, and agent teams should be small and shut down when finished.
• CLAUDE.md loads into every session. Anthropic suggests keeping it under 200 lines and moving long workflow instructions into skills, which only load when used.

On the Free plan

Free has much lower limits, so the same habits matter more. New chat per topic, no unnecessary attachments, one well-planned message instead of five quick ones. If you regularly hit the limit mid-task, that's the signal Pro is worth it. Anthropic doesn't publish exact message counts for any plan, because usage depends on the factors above.

Pro or Max?

If you hit the five-hour limit most days, especially in Claude Code, Max is the straightforward fix. If it's the weekly limit, as it was for me, I'd look at /usage for loops, sessions that never close and Opus-heavy work before paying more.

Last checked: 19 October 2026. Limits and menus change often. I'll update this page when they do.

Sources

• Claude Help Center: How do usage and length limits work?
• Claude Help Center: Usage limit best practices
• Claude Help Center: Manage usage credits for paid Claude plans
• Claude Help Center: What is the Max plan?
• Claude Code docs: Manage costs effectively
• Anthropic: Higher usage limits (6 May 2026)