Guides
Short, practical posts on surviving Claude plan limits, weekly quotas, and the 5-hour window.
71% Weekly Quota by Monday on One Opus Refactor: Local Estimators Off by 30%+
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.
Active Recall Study Sessions and the Claude 5-Hour Window: Where the Usage Goes
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
Anthropic Shortage, Cache Bust, Funny Money: Why Your Make-Good Credits Are Already Spent
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.
chatgpt.com/codex/pricing Explained: What OpenAI Codex Costs in 2026
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.
Claude Agentic Loop Usage Limit: The seven_day_oauth_apps Bucket Almost Nobody Names
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
Claude Code /goal feature: why it burns the weekly quota faster
/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.
Claude Code + Codex Token Juggling: Two CLIs, One Plan-Shape, Independent Clocks
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.
Claude Code 4.7 Rate Limit: The Eight Floats On One Endpoint, Four Of Them Hidden
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
Claude Code 4.7 Regressions: The One That Shows Up in Your Quota, Not Your Benchmarks
The loudest Claude Code 4.7 regression isn
Claude Code 5-Hour Rate Limits Doubled (May 6, 2026): the Weekly Cap Is the New Wall
Anthropic doubled Claude Code
Claude Code as a personal OS: which weekly quota bucket your routines actually drain
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.
Claude Code context overhead: ~7,850 tokens before you type, and the part nobody tells you about your weekly quota
Anthropic
Claude Code cost per landed PR: the yield-adjusted formula your ccusage report skips
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.
Claude Code Cost Per PR: What a Pull Request Actually Burns on Pro or Max
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
Claude Code dollars per pull request: the only field on Anthropic
There are three different
Claude Code hang vs rate-limit: which status signal is actually telling you the truth
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.
Claude Code Max usage limits: the published numbers, and the float they actually come from
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.
Claude Code model regression visibility: the DIY monitor you can run in one shell script
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 Opus 4.7 Usage Limits: The Two Server Floats That Gate You
Claude Code
Claude Code Opus cost per PR: the one field that actually moves, and why the menu-bar badge hides it
On a Pro or Max plan, the Opus cost of a PR is the delta on seven_day_opus.utilization alone. ClaudeMeter
Claude Code Opus token usage: the local-token sum and the server fraction never match (and only one decides your next 429)
Claude Code on Opus has two different
Claude Code Pro usage: the buckets, the math, and why ‘45 messages’ is the wrong unit
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.
Claude Code rate limit: 8 quota floats on one endpoint, 4 of them hidden
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 rolling 5h + weekly quota: it is four clocks, not two
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.
Claude Code rolling 5h wall + MCP overhead: the cache-miss math nobody walks you through
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.
Claude Code Senior Reviewer Workflow: The seven_day_opus Float Is Your Reviewer Budget
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.
Claude Code Spillover to OpenRouter: Flip Before the 429, Flip Back After Reset
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.
Claude Code team dollar burn: the real number lives in one field ccusage can
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.
Claude Code Usage in the macOS Menu Bar: The Two-Tier Redraw That Keeps the Dropdown From Snapping Shut
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.
Claude Code usage tracker: there are two of them, and only one knows when your loop will 429
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.
Claude Code weekly limit during long workflows: pre-flight, mid-flight, abort
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 weekly quota meter: the meter you watch instead of typing /usage
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.
Claude Extra Usage Balance: What the Dollar Line on /settings/usage Actually Is
The
Claude Max 5-hour rolling window: how it is server-tracked, not counted
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.
Claude Max Plan Still Hitting Limits? It Is Eight Buckets, Not One
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.
Claude Max rolling 5-hour weekly limit: the two limits are actually four
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.
Claude Max third-party usage tracking: the two server fields you actually need after April 4, 2026
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.
Claude Max usage tracking: it is seven counters, not one, and most trackers only show two of them
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.
Claude Max weekly limit tracker: it
The weekly limit on Claude Max isn
Claude Max Weekly Quota Tightening: The Weekly Bucket Didn
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.
Claude Opus 4.7 Rate Limit: The Three Endpoints That Decide Your Next Request
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.
Claude Pro 5-Hour Window Quota: What the Server Actually Counts
Pro
Claude Pro 5-Hour Window Visibility: One Worst-Case Number on Your Toolbar
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 rate limits as a budget: the free quota and the dollar cap, side by side
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 Usage Limit: The Eight Buckets the Server Actually Tracks (2026)
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.
Claude Pro Usage Limits on Reddit: What r/ClaudeAI Says vs What the Server Tracks (2026)
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.
Claude Pro Usage Meter for Browser Automation Workflows: A claude-meter --json Loop Guard
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.
Claude Pro VAT charges explained: the two fields that decide what you are billed in the EU and UK
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.
Claude Pro weekly quota and
Anthropic estimates 40 to 80 hours of Sonnet per week on Pro, but never names the threshold for
Claude Pro Weekly Quota Tracker: What the 7-Day Row Actually Shows
On a Pro plan the weekly quota tracker is one popup row:
Claude Pro Weekly Quota Wall Mid-Refactor: A 90-Second Recovery Playbook
Claude Code just killed your refactor at 100% weekly. Here is what to read off ClaudeMeter
Claude programmatic usage tracker before June 15: the OAuth endpoint Anthropic does not document
June 15, 2026 is the Sonnet 4 / Opus 4 deprecation deadline. Anthropic
Claude Rate Limit Dashboard for Pro and Max: What It Has To Render, Field by Field
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.
Claude Rolling 5-Hour Burn Rate: Δu/Δt, Not Tokens per Minute
The only correct burn rate for Claude
Claude rolling 5-hour reset: there is no single reset, each message ages off on its own clock
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.
Claude Server Quota Visibility: Why Token Counters Cannot See What Anthropic Actually Enforces
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.
Claude Session Window Monitor: Why You Are Watching Seven Clocks, Not One
Anthropic
Claude Usage Meter for Parallel Agents: One Server Bucket, N Agents, dedupe_by_account
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
Claude usage tracker gone: the three failure modes and what is actually broken
When
Claude Weekly Limit and Extra Usage: The Fall-Through Chain, Field by Field
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.
Claude Weekly Limit by Tuesday: It
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.
Claude Weekly Quota Silent Tightening Tracker: What a Real One Needs to Do
Silent tightening is a server-side weight change, not a token change. A tracker that reads local Claude Code logs can
Claudmeter: the product you mean is ClaudeMeter (claude-meter.com)
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: you meant ClaudeMeter (the free Claude plan usage tracker)
'Clawdmeter
New Claude Models in April 2026 and What Each One Did to Your Usage Limits
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
Open Source Claude Usage Trackers (April 2026): A Field Guide That Splits Local-Log From Server-Truth
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:
Rolling 5-hour window: how Claude Code actually behaves before, at, and after the wall
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
Rolling Window vs Metered Billing on Claude: Two Parallel Systems, Not Two Stages
Claude
The Claude 5-Hour Server-Side Wall Is Three Walls, Not One
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.
The Claude Code rolling 5-hour wall is one float on one endpoint
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.
The Claude Code Weekly Quota Wall: Claude Code Already Knows, It Just Won
When the weekly wall fires, Claude Code prints a generic
The Claude Rolling Window Cap Is Seven Windows, Not One
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.
The Claude Weekly Quota Server-Truth Meter (and Why Its Number Cannot Disagree With claude.ai)
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.
Tracking Claude + Exa Search Usage: Two Bills, Two Meters
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.
What is seven_day_omelette? The Claude Design weekly quota bucket, explained from the API
seven_day_omelette is the rate-limit field for Claude Design