Free calculator

How close are you to your Claude Code usage limit?

Set your plan and usage pattern below and see your modeled burn rate, risk factor, and projected headroom across Pro, Max 5x, and Max 20x.

Plan you're on (or comparing from)
Sessions you run in a typical day3
Typical workload
Active days per week5
Sessions before "usage limit reached" on this plan
Do you /clear between unrelated tasks?
Full files, or paths?
1.80Mtokens / day at this pace
9.00Mtokens / week across 5 active days
Low risk

Neither documented drain habit applies - your burn rate should track your actual work.

Enter how many sessions you usually get before "usage limit reached" above to project headroom across Pro, Max 5x, and Max 20x - Anthropic confirms Max multiplies Pro's room by 5x or 20x, but doesn't publish an absolute size for either budget to calculate a percentage from.

This projects headroom from a number you supply. Run the free scan to see what's actually driving your real sessions instead of estimating it.

npx usagecutRun a free scan
Recommended next step

A clean setup is just the beginning.

UsageCut trims that for free. Want Claude Code to be genuinely better, not just leaner? ClockedCode is the curated, conflict-free setup - installed in one paste.

Upgrade your Claude Code
  • 10x your Claude Code with hand-picked tools
  • Specialist agents on your team
  • Stop spending hours researching plugins
How this projection works

Relative headroom, not an invented percentage

Anthropic confirms the shape of a Claude Code plan's usage ceiling - a rolling five-hour session window plus a separate weekly budget, with Max 5x and Max 20x buying roughly 5x and 20x Pro's room in both - without ever publishing an exact size for either budget, on any plan, Pro included. That's covered in full in Claude Code Pro plan usage limits, explained. A calculator that shows a percent-of-budget number here would have to invent the denominator, so this one asks for a number you actually know instead - roughly how many sessions you get before hitting the wall - and projects that same headroom across the other two tiers using Anthropic's own confirmed multiplier.

The risk factor comes from the two specific habits Claude's support docs name as the fastest ways to burn a session's budget early: skipping /clear between unrelated tasks, and pasting full files into a message instead of pointing Claude at their paths. The full breakdown of why those two matter more than most people expect is in why Claude Code says "usage limit reached".

This is still a projection, not a live reading. For the exact number right now, open /usage inside Claude Code, or see what a session actually costs in dollars with the Claude Code cost calculator. For your real setup waste instead of a modeled pattern, run the free UsageCut scan.

Free tools

More free tools for Claude Code

Small, focused, no-signup tools from the maker of ClockedCode. Free to use, forever.

UsageCutScan your real Claude Code setup and see exactly where your tokens are wasted, then cut it losslessly.Claude Code Cost CalculatorEstimate your monthly Claude Code cost from sessions per day and workload, and see whether Pro, Max, or API pricing wins.CLAUDE.md Token CounterPaste your CLAUDE.md or AGENTS.md to count its tokens and see which sections look conditional enough to move out.MCP Server Token Cost CheckerPaste your mcpServers config to see the estimated token cost per server, worst first, with tool-search deferred loading on or off.CLAUDE.md GeneratorAnswer a few questions about your stack and get a CLAUDE.md scoped to just that, with a live token cost per section.Context Window CalculatorSee what percent of your context window is used, your headroom before compaction, and the cache-read cost of carrying it.Subagent Cost CalculatorSee whether spawning N Claude Code subagents actually saves tokens versus doing the same work in one session, using the measured 216-token subagent overhead.Token Usage AnalyzerPaste lines from a Claude Code session transcript to see the token breakdown by cause: conversation text vs tool output, tool output by Read/Bash/agent calls, and duplicate file reads.Best MCP Servers for Claude CodeBrowse popular Claude Code MCP servers by category and see each one's estimated token cost per session, sorted worst to best.Hook Token Cost CalculatorPaste your hooks config to see the estimated token cost per hook, worst first, classified by how often each event actually fires.Tool Search Token Savings CalculatorPaste your mcpServers config to see how many tokens Claude Code's tool search saves by deferring schemas, and whether a custom auto:N threshold would load them upfront instead.Opus vs Sonnet Cost CalculatorSee the dollar gap between running Claude Code on Opus vs Sonnet, plus the honest (not naive) savings from pinning just the Sonnet-safe turns.Claude Code Model PickerAnswer 5 questions about your current task to get a straight verdict: stay on Opus, hand it to a Sonnet subagent, or use opusplan.Which Claude Plan Should You UseAnswer a few questions about your usage and team size to get a straight Pro, Max, Team, or Enterprise recommendation with real current pricing.Compaction Cost CalculatorSee how many times a Claude Code session will hit auto-compact and what each compaction actually costs in tokens, cache-warm or cold.

More free Claude Code tools are on the way - built one at a time by a solo dev who ships daily.

Built for developers using Claude Code every day - by a solo dev who ships daily and uses this on his own setup.

Open-source scanner, runs locally, your code never leaves your machine.

Claude Code tips, every Sunday

One short email a week: the token-saving tricks, setup tweaks, and tools worth your time. Free, unsubscribe anytime.

Calculator FAQ

About this projection

Is this my exact usage limit, or an estimate?

An estimate, and an honest one about what it can't know: it models your daily and weekly token burn from a pattern you set, then projects headroom across plans from a number you supply - roughly how many sessions you've gotten before hitting "usage limit reached." For your real, live number, open /usage inside Claude Code or run the free scan below.

Where does the 5x / 20x multiplier come from?

Anthropic's own docs, checked directly against support.claude.com and claude.com/pricing while writing our Pro plan usage limits guide (fetched 2026-08-05): Max 5x gives roughly 5x Pro's room and Max 20x roughly 20x, across both the 5-hour session window and the separate weekly budget. It's the one sizing fact Anthropic actually confirms about plan tiers.

Why doesn't this show a percent of my budget, like the context window calculator does?

Because that number doesn't exist to divide by. Claude Code's context window has a published size (200K or 1M tokens depending on model and plan), so a percent-used figure is real math. The 5-hour and weekly usage budgets don't have a published size on any plan, Pro included - a tool that shows a percentage here would be inventing the denominator. This one projects relative headroom from your own observed baseline instead.

How is the risk factor calculated?

From the two specific habits Claude's own support docs name as budget drains, also covered in our usage-limit-reached guide: not clearing between unrelated tasks, and pasting full files into a message instead of pointing Claude at their paths. Neither checked is Low, one is Medium, both is High - it's a flag for which documented habit to fix first, not a token-precise multiplier.

FAQ

Questions, answered

Is UsageCut really free?

Yes. The scan and every fix are free - no card, no subscription, no signup. You only give an email if you want the optimization plan and one-command undo sent to your inbox.

Is my code safe? Does UsageCut upload anything?

The scan runs entirely on your machine. It never uploads your code, never reads your API key, and never sends your prompts or conversations anywhere. Only anonymous summary counts leave, and only if you choose to share them.

How does it reduce Claude Code token usage?

It reads your local setup and session history to find waste - idle MCP servers loaded into every session, an oversized CLAUDE.md re-sent on every request, duplicate file reads, and bloated tool output - then trims it losslessly, so each session carries less context and you hit your limit far less often.

What is ClockedCode?

ClockedCode is the curated, conflict-free Claude Code setup from the same maker. UsageCut makes your current setup leaner; ClockedCode makes it genuinely better - a set of hand-picked tools, specialist agents, and a tuned CLAUDE.md, installed in one paste.

Who is ClockedCode for?

Developers who use Claude Code daily and want a setup that is powerful out of the box instead of spending hours researching and wiring up plugins, agents, and MCP servers themselves.

What's included in ClockedCode?

A vetted, conflict-free bundle of hand-picked tools, specialist agents, and a tuned CLAUDE.md - everything installed together in one paste, with no setup archaeology.

Is ClockedCode a one-time payment?

Yes. ClockedCode is a one-time purchase with an instant download - no subscription and no recurring fees.

Does ClockedCode work with my existing setup?

Yes. It installs alongside what you already have and is fully reversible. Run UsageCut first to clean your current setup, then add ClockedCode to level it up.