Sitemap

One Monday Opus refactor burned 71% of the rolling weekly Claude quota. Local token estimators were off by 30%+. The April 2026 metered billing transition is catching Pro and Max users off guard. claude.ai/settings/usage is the only honest number.

Quizzing yourself with Claude Pro burns the rolling 5-hour window faster than the card count suggests, because each new question carries the growing transcript. Here is the mechanic, the JSON the server returns, and how to schedule a study break around the reset instead of around the

The credits Anthropic handed out during the 2026 compute shortage and the Claude Code cache TTL drop are denominated in dollars, but the same /api/organizations/{org}/overage_spend_limit response that lists them ships an out_of_credits flag and a disabled_until timestamp the server can flip silently. ccusage cannot see either field. ClaudeMeter does.

Codex is bundled into ChatGPT plans, not sold separately: Free $0, Go $8, Plus $20, Pro from $100, Business pay-as-you-go. Here is a plain reading of the official pricing page, what the April 2026 token-rate change did, and the usage windows the sticker price never shows you.

An agentic loop on a Claude Pro or Max plan does not move one usage counter. It moves a specific server-side bucket called seven_day_oauth_apps inside /api/organizations/{org}/usage, with its own utilization fraction and its own resets_at, and that

/goal lets Claude Code run unattended turn after turn until a Haiku-evaluated condition is met. Anthropic doubled the 5-hour cap in May 2026 but left the weekly cap unchanged, so /goal sessions wall on seven_day_oauth_apps days earlier than interactive use. Here is the math, the bucket to watch, and the guards.

Both Claude Code and Codex now ship the same plan caps: a rolling 5-hour bucket plus a weekly bucket. They reset on different clocks. Here is the juggle pattern that uses that asymmetry, and the one piece of plumbing it needs to actually work proactively.

The Claude Code 4.7 rate limit is not two numbers. The /api/organizations/{org}/usage endpoint returns eight utilization floats, and claude.ai/settings/usage renders only four of them. ClaudeMeter

The loudest Claude Code 4.7 regression isn

Anthropic doubled Claude Code

The Context-Connections-Capabilities-Cadence playbook tells you how to run Claude Code while your laptop is closed. It does not tell you which of the seven weekly buckets those runs charge against, or why your local tracker thinks you have plenty of quota left while the server has already walled you.

Anthropic

Cost per PR and cost per landed PR are different numbers. Quota burned on abandoned branches, failed CI retries, and force-pushes never refunds. Here is how to window ClaudeMeter utilization samples against git log --merges to get the real denominator.

On a Claude Code subscription the real cost of a PR is not a dollar figure. It is the delta in seven_day_opus.utilization between your first and last commit. Here is the formula, the endpoint, and why ccusage

There are three different

When Claude Code freezes mid-edit, the status line, the /status command, and the spinner are all local signals. None of them can tell you if Anthropic has rate-limited you. The one signal that can lives on the server.

Anthropic does not publish a prompt count for Max. Every Claude Code Max user is rate-limited by a utilization float on claude.ai/api/organizations/{org_uuid}/usage. Here is the float, the prompt ranges the float maps to after the May 6, 2026 doubling, and what stayed the same.

Model regressions ship silently. ~/.claude/projects/*.jsonl cannot see them because Anthropic applies the expensive changes (tokenizer swaps, hidden thinking tokens, quota inflation) server-side, after your client has already moved on. ClaudeMeter

Claude Code

On a Pro or Max plan, the Opus cost of a PR is the delta on seven_day_opus.utilization alone. ClaudeMeter

Claude Code on Opus has two different

On the $20 Pro plan, Claude Code shares one rolling 5-hour bucket and one weekly bucket with claude.ai web chat. The server measures both as a utilization float on /api/organizations/{org}/usage, not as a message count. Here is the JSON shape, the per-model sub-buckets the help center omits, and how a Pro Code user actually walls.

The Claude Code rate limit is not one number. It is eight utilization floats on claude.ai /api/organizations/{org_uuid}/usage. Any one of them at 1.0 returns 429. claude.ai/settings/usage only renders four. Here are the field names, why ccusage cannot see them, and the one-line install that shows all eight.

Claude Code charges four independent rolling buckets per turn, not two. The fourth one, seven_day_oauth_apps, is Claude Code + MCP only and claude.ai/settings/usage does not display it. Here is the field list, why it bites Code-heavy users first, and how to read the live numbers in 60 seconds.

A typical Claude Code 5-hour window has 8 to 15 cache-miss turns. Each one re-bills your full MCP tool definition payload at cache-write rate (25% over input). So 30,000 tokens of MCP overhead can cost 240,000+ extra input-equivalent tokens against the rolling 5-hour bucket. Here is the math, the source struct that watches the bucket, and the fastest way to see when MCP is the wall.

The two-agent senior-reviewer pattern (Sonnet worker, Opus reviewer) is rationed by one hidden number: seven_day_opus.utilization. It lives at src/models.rs line 23 in ClaudeMeter and you can read it from a shell via claude-meter --json. Every other write-up is a prompt template; none of them tell you when your Thursday reviewer calls will 429.

How to spill Claude Code over to OpenRouter when your Pro/Max plan caps, what env vars to set, and the 12-line shell hook that uses claude-meter --json to flip BEFORE you hit a 429 and flip back the moment the 5-hour clock resets.

If your team runs Claude Code on individual Pro/Max plans, the only real dollars are the flat subscription plus metered extra-usage. ccusage shows an estimated token price you never pay. Here is where the actual billed dollars live and how to sum them across seats.

ClaudeMeter is the macOS menu bar app for Claude Code usage. Free, open-source, brew install --cask m13v/tap/claude-meter. The unique part is the redraw strategy: title repaint every minute (cheap), menu rebuild only when the account set changes (expensive). That branch at src/bin/menubar.rs lines 137-146 is why the dropdown stays open while you watch a long Claude Code run burn through the 5-hour window.

Most Claude Code usage trackers count the local tokens you sent (ccusage, Claude-Code-Usage-Monitor). The number that actually 429s your loop is a server-side utilization on /api/organizations/{org}/usage. ClaudeMeter is the open-source tracker that reads it directly from the browser cookie you already have. Run both.

Long Claude Code refactors do not wall on the seven_day bucket. They wall on seven_day_oauth_apps, which is why the CLI 429s while claude.ai web chat in the other tab keeps working. Here is the pre-flight check, the live signal to watch, and the abort threshold.

Claude Code already has a /usage slash command. It is one-shot, it interrupts the loop, and it only prints the active session window. A meter polls the same /api/organizations/{uuid}/usage endpoint once a minute outside of Claude Code, so you watch the seven weekly buckets accrue without breaking your agentic loop.

The

On Claude Max the 5-hour window is not a prompt counter. The server tracks it as a single utilization float that it recomputes continuously over a rolling age-off, which is why your bar can move while you send nothing. Here is the field, the endpoint, and why local token tools cannot see it.

Max does not unlock unlimited. Anthropic enforces eight independent server-side gates and any one of them stops the next prompt. Here is the 60-second triage to find which one fired and what to do.

On Claude Max, the rolling 5-hour window and the weekly cap are not two limits, they are four+ independent utilization windows that each fire their own 429. Here is the exact field list, the May 6 2026 doubling, and how to read the live numbers.

Since April 4, 2026, Claude Max no longer covers third-party tools (Cline, Roo Code, aider, OpenCode, Cursor) under the plan; those calls bill at per-token API rates against extra_usage. Tracking it now means watching two fields on /api/organizations/{org}/usage at once: seven_day_oauth_apps.utilization and extra_usage.used_credits. Here are both, where they live in the JSON, and how to read them live.

A Claude Max plan is metered by seven independent utilization windows plus an extra-usage block, all returned by claude.ai/api/organizations/{org}/usage. Most browser extensions and CLI tools collapse them into a session bar and a weekly bar. Here is the full shape, why each bucket bites you, and how ClaudeMeter exposes all of them.

The weekly limit on Claude Max isn

Everybody calls the 2026-03-26 change a weekly quota tightening. The claude.ai usage endpoint says otherwise: seven_day.utilization tracks flat while five_hour.utilization climbs 1.4x-2x faster on weekdays 13:00-19:00 UTC. Here is how to watch the slope change live.

The Opus 4.7 rate limit is not one number. It is a three-endpoint decision tree on claude.ai: /usage returns the utilization floats, /overage_spend_limit says whether paid fallback is live, /subscription_details pins your plan ceiling. ClaudeMeter polls all three and exposes them on a localhost bridge at 127.0.0.1:63762.

Pro

ClaudeMeter shows the worst five-hour utilization across every Anthropic org you belong to as a single colored badge on your browser toolbar, refreshed every 60 seconds from the same JSON the claude.ai Settings page itself fetches.

Claude Pro now has two stacked budgets. The free one is the 5-hour rolling window plus the weekly cap. The dollar one is the metered-billing limit you set at claude.ai/settings/usage. Most rate-limit guides only cover the first. Here is how the second one works, where the number lives, and how to watch both at once.

Claude Pro is not one limit. The claude.ai server returns eight separate utilization buckets, two of them undocumented, and any one at 100% throttles your account. The verified numbers, the bucket names, and the field that anchors them.

The most-upvoted Reddit complaints about Claude Pro limits, mapped to the eight utilization buckets the claude.ai server actually returns. Real thread links, the bucket each gripe is about, and what redditors do about it.

Browser automation against Claude Pro / Max burns through the rolling 5-hour window in minutes. ClaudeMeter exposes the server-truth quota via claude-meter --json and a 60-second auto-refreshing extension, so a Playwright, Computer Use, or Claude Code loop can read its own utilization mid-run and pause before Anthropic returns 429.

Anthropic computes Claude Pro VAT from your billing address, and the country it has on file surfaces in two fields on the internal subscription_details endpoint: payment_method.country and currency. Here is how to read them, how to change your billing address or add a VAT ID, and what each country code turns $20 into.

Anthropic estimates 40 to 80 hours of Sonnet per week on Pro, but never names the threshold for

On a Pro plan the weekly quota tracker is one popup row:

Claude Code just killed your refactor at 100% weekly. Here is what to read off ClaudeMeter

June 15, 2026 is the Sonnet 4 / Opus 4 deprecation deadline. Anthropic

Anthropic does not ship a rate-limit dashboard to individual Pro and Max subscribers. The Console analytics surface is Team and Enterprise only. So a real Pro/Max rate-limit dashboard has to be assembled from claude.ai/settings/usage. Walking the eight floats, the color thresholds (RGB 219,118,32 at 90 percent and RGB 215,58,73 at 100 percent), the multi-account tile composition, and the localhost bridge on 127.0.0.1:63762 that wires a browser extension into a native menu bar.

The only correct burn rate for Claude

The rolling 5-hour window does not reset to 0% all at once. Each message you send has its own 5-hour age-off clock. The resets_at timestamp at claude.ai/settings/usage is just when the oldest message in the window falls off, not when utilization returns to zero.

The server returns utilization as a dimensionless fraction with a private denominator. Token counters like ccusage have the numerator but not the denominator, so their number cannot equal the quota the server enforces. Here is what to read instead.

Anthropic

Five Claude Code agents running in five worktrees do not get five quotas. They share one server-side rolling 5-hour bucket and one seven_day_oauth_apps weekly bucket per account. ClaudeMeter

When

When the Claude weekly bar hits 100%, what happens next is decided by three values across two undocumented endpoints: extra_usage.is_enabled, used_credits vs monthly_credit_limit, and out_of_credits. Here is the full decision tree, the JSON at every state, and the boolean that tells you whether you are blocked or still spending.

Your Claude weekly limit hits by Tuesday because the seven-day bucket is a rolling 168-hour window keyed off your first message of the cycle, not a calendar week. The exact cliff timestamp is the seven_day.resets_at field at claude.ai/api/organizations/{org}/usage. Here is how to read your own and how to shift the next cycle.

Silent tightening is a server-side weight change, not a token change. A tracker that reads local Claude Code logs can

Guides on surviving Claude Pro and Max plan limits: rolling 5-hour windows, weekly quotas, extra-usage pricing, menu bar workflow tips, and Claude Code patterns.

Claudmeter is a common misspelling of ClaudeMeter, the free open-source macOS menu bar app that shows your live Claude Pro and Max plan usage. Same product, missing one e. Here is what it is, the brew install, and how it differs from ccusage.

'Clawdmeter

Three Anthropic announcements in April 2026 touched plan usage limits in three different ways: Mythos Preview on Apr 7 (Glasswing partners only, no Pro/Max impact), Opus 4.7 on Apr 16 (same denominators but 1.0x to 1.35x faster fill from the new tokenizer), and the Apr 23 postmortem (every subscriber

Seven open source trackers for Claude Pro, Max, and Claude Code, sorted by what they actually read. Local JSONL versus the same private endpoint claude.ai/settings/usage renders. Which require a sessionKey copy-paste, which use an embedded webview, and the only one that uses your real browser cookie via credentials:

The rolling 5-hour window is not a 5-hour timer. Each message you send is in-window for exactly 5 hours from when you sent it, then ages out. Claude Code keeps sending until the server

Claude

When Claude Pro or Max 429s you at the 5-hour mark, three separate server-side conditions can produce identical-looking errors. Here is where each one lives in the JSON, why overage_spend_limit has its own suspension clock, and how to reconstruct the full wall state from the endpoints the Settings page hides.

When Claude Code 429s your refactor at the 5-hour mark, the wall is literally one f64 (five_hour.utilization) on one server endpoint. Here is the exact field, why ccusage and /usage cannot see it, and what to do the moment your loop stops.

When the weekly wall fires, Claude Code prints a generic

Anthropic does not enforce a single rolling window on Pro and Max plans. The internal usage endpoint returns seven stacked buckets, each with its own utilization and reset timestamp. Here is what each one is, where it lives in the schema, and why you get rate-limited before the Settings page looks anywhere near full.

ClaudeMeter is the free, open-source macOS menu bar that reads your weekly quota from the same HTTPS call your /settings/usage page makes on reload. Same cookie, same Referer, same JSON. Here is the call site, the response shape, and how to verify the number in 30 seconds.

Exa charges you per search via costDollars. Claude charges you tokens for ingesting the result text, which lands on the rolling 5-hour window and weekly quota. No single tracker shows both. Here is the field, the shape of each bill, and how to read them in parallel.

seven_day_omelette is the rate-limit field for Claude Design

Drop your email, get the brew command and .dmg link in your inbox. Free, MIT, macOS 12+. Reads your existing claude.ai session, no cookie paste. Menu bar gauges for 5-hour, weekly, and extra usage in about a minute.

How ClaudeMeter talks to claude.ai to read your Pro/Max plan quota, why the numbers match the usage page, and what data leaves your machine (nothing).

Answers to common questions about ClaudeMeter: safety of the browser extension, Safari support, differences from ccusage, and whether Anthropic allows it.

ClaudeMeter reads your Claude plan quota from claude.ai (server-truth). ccusage reads local Claude Code JSONL token logs. Different data; many people run both.

ClaudeMeter is local-first: usage data stays on device, with anonymous crash reporting and daily active telemetry that can be disabled.

The Pro/Max plan walls you mid-PR when five_hour.utilization crosses 1.0. The API never walls but has unbounded cost variance. Most guides reduce this to a static break-even number (Max wins above $100/mo). The harder variable is which failure mode you can tolerate. ClaudeMeter prints both gauges as sibling rows in the menu bar because format.rs handles them as two different units.

Two separate caps. The rolling 5-hour is a sliding burst limit (~45 messages on Pro, resets continuously as old prompts age out). The weekly quota is a 7-day compute ceiling (~40-80h on Pro, shared across claude.ai chat, IDE, and Claude Code). On the server they are sibling fields on the same JSON, and either can independently kill your loop.

Claude Code and claude.ai chat both deplete one shared org-scoped 5-hour and 7-day bucket on the server. But a Claude Code agentic loop typically drains the bucket 5-10x faster per wall-clock minute than the same minute in chat, because each turn fans out into tool calls, file reads, and multi-turn replays. ClaudeMeter polls both endpoints (api.anthropic.com/api/oauth/usage for Code, claude.ai/api/organizations/{org}/usage for chat+everything) and shows the seven_day_oauth_apps sub-bucket so you can see exactly which surface is burning your week.

Free is one opaque daily-style cap, Sonnet only, no usage page worth checking. Pro is a rolling 5-hour window plus a weekly quota and, on the server, an 8-bucket JSON object that ccusage cannot see and that the Settings page only half-renders. Verified Free vs Pro numbers and the actual data shape.

The Max plan bar is a percentage on /api/organizations/{org}/usage. The extra usage line is dollars on /api/organizations/{org}/overage_spend_limit. They run side by side, on different endpoints with different units. The bar can be at 100% while extra usage is at $0; extra usage can be spending while the bar shows green. ClaudeMeter renders them as sibling rows because that is what they are.

The JSON Claude Code pipes to your statusLine script only carries context_window.used_percentage. To show the 5h and 7d utilization Anthropic actually rate-limits on, your script has to shell out to

ccusage attributes one token sum to wall-clock time. Anthropic

A meter and a dashboard are not substitutes for each other. A meter pushes one float into your peripheral vision so you decide whether to keep prompting right now. A dashboard sits behind a deliberate visit so you can answer where your week went. Walking the structural difference, the two-tier redraw at src/bin/menubar.rs lines 136-146 that makes the meter pattern actually work, and why most heavy Claude Code users end up running both.

Context compression (auto-compact) is a local 200K-token conversation mechanic. Plan quota is the server-side rolling 5-hour and 7-day budgets Anthropic enforces against your account. Compacting does not refund plan quota; per Anthropic

Your ~/.claude/projects/*.jsonl files only record input_tokens and output_tokens per turn. The server adds five weights on top (peak-hour multiplier, attachments, tool calls, model class, browser chat) and exposes the result as five_hour.utilization at claude.ai/api/organizations/{org}/usage. That is why ccusage says 5% and claude.ai still 429s you.

Your ~/.claude/projects/*.jsonl is a token diary, not a quota statement. The number Anthropic rate-limits on lives at claude.ai/api/organizations/{org}/usage. Cat the file, curl the endpoint, and watch them disagree on the same minute.

Most VS Code + Claude Code workflow guides walk through panels, @-mentions and permission modes, then leave you to discover the rolling 5-hour wall mid-refactor. The Anthropic extension exposes /usage as a one-shot lookup. claude-meter pins the same number live in your menu bar so the meter stays in your peripheral vision while you keep typing.

Dated roundup, April 23, 2026. Eight tools for the week you are watching your Claude Pro or Max quota. Ranked by whether they read Anthropic

Claude Meter Pro is a proactive AI agent that watches your Claude Code and Claude.ai sessions, finds places where you can spend less of the 5-hour and weekly quota without losing output quality, and (with your permission) implements the fixes for you. Join the waitlist.

All pages on ClaudeMeter: install, how-it-works, FAQ, comparison, privacy, and every guide published under /t/.