Stop finding out about Claude Code regressions from Reddit threads three weeks later

The JSONL is written by the CLI at the moment of the call, using token counts the client computed before the server touched the payload. When Anthropic rolls out a new tokenizer, switches the default thinking budget, or redacts thinking content (as happened on 2026-02-12), none of those changes propagate back into the JSONL. ccusage and Claude-Code-Usage-Monitor both read that file, so they both keep showing pre-expansion counts. The quota, the invoice, and the 429 all come from a separate float Anthropic writes server-side: usage.seven_day_opus.utilization on /api/organizations/{org}/usage. That float is the only number that can tell you a regression has landed.

It is a localhost HTTP server the ClaudeMeter menu-bar app runs on the loopback interface. The browser extension POSTs a parsed UsageResponse snapshot to it every 60 seconds (POLL_MINUTES = 1 in extension/background.js line 3). The same server answers GET /snapshots with a JSON array of recent snapshots. That dual interface is what makes a scriptable monitor possible: the extension authenticates with your existing claude.ai cookies so no API key management exists, and the shell can still read the result without ever touching claude.ai. A before-prompt curl plus an after-prompt curl, minus one another, is a regression probe.

The UsageResponse struct in src/models.rs lines 19 to 28 has seven Option<Window> fields plus extra_usage. The three that matter for regression attribution are five_hour (shared across every model), seven_day_sonnet (Sonnet-only lane), and seven_day_opus (Opus-only lane). A regression that only affects Opus traffic will move seven_day_opus.utilization while leaving seven_day_sonnet flat on an idle Sonnet bucket. A regression that changes the tokenizer for every model will move all three by the same ratio. A regression that doubles the hidden-thinking budget will move the Opus lane faster than the five-hour shared lane for the same prompt. This is why isolating the lanes matters.

Three steps. (1) Capture a baseline: curl -s http://127.0.0.1:63762/snapshots | jq '.[0].usage.seven_day_opus.utilization' and write it to a file. (2) Run the prompt through Claude Code in a fresh session so nothing else is inflating the bucket. (3) Capture the post-prompt snapshot the same way. The delta between (3) and (1), divided by the prompt's local token count from ~/.claude/projects/*.jsonl, is your server-to-client cost ratio for that call. A stable ratio across prompts means no regression. A ratio that jumps 20 percent overnight on the same corpus is your regression signal.

Two safeguards. First, the ClaudeMeter extension polls every 60 seconds, so if you run your prompt and capture the after-snapshot within the same polling window, you'll see the fresh float. Second, UsageResponse has three separate windows, so you can cross-check: a real 4.7-specific regression should move seven_day_opus but leave seven_day_sonnet untouched if you only issued Opus traffic. If both move, you have ambient traffic on the account (another client, another device, a scheduled job) or a tokenizer-wide regression. Both explanations are informative.

Claude Code's OpenTelemetry export publishes client-side metrics: token counts as the client computed them, tool-use counts, latency. Those are useful for behavioral regressions (the signature-thinking correlation analysis that caught the 2026-02-12 redaction used a similar shape of data). They are not useful for quota regressions because they report the same pre-expansion number the JSONL already has. The bridge is the complement: it reports what Anthropic's server wrote to the account's quota after the model ran. You want both. OTEL tells you what the client thinks happened; the bridge tells you what the server charged you for.

ClaudeMeter reads the exact same endpoint the claude.ai/settings/usage page reads to render its own bars. The extension authenticates with your existing browser cookies and polls once per 60 seconds, the same cadence the settings page uses when open. No API key is involved and no rate limit is implied by Anthropic beyond the public per-IP limits. The endpoint is undocumented, so it can change. ClaudeMeter parses into strict Rust structs (models.rs) so a schema break surfaces as a parse error on the menu bar, not as silent wrong numbers.

Two worth naming. (1) The 2026-02-12 thinking redaction: a silent UI-layer change that hid thinking content, which downstream users analyzed across 17,871 thinking blocks and 234,760 tool calls to prove that tool usage had measurably shifted to 'edit-first' patterns. A bridge diff would have caught the same event as a shift in output-token delta per prompt on Opus traffic within hours. (2) The 4.7 tokenizer expansion: the same prompt on 4.7 consumes more seven_day_opus than on 4.6 because the new tokenizer expands text by up to roughly 35 percent. The bridge reports the post-expansion float; the JSONL reports the pre-expansion count. The gap between them is the size of the regression.

Only subscription plans. The /api/organizations/{org}/usage endpoint is the account-level quota service that backs Pro, Max 5x, and Max 20x. API billing uses per-token metering on a separate system that does not populate the seven_day_* windows. If you run Claude Code against an API key, regressions show up as a higher invoice, which you can still read from your Anthropic console billing page. The bridge protocol described here is specifically for the subscription-plan quota lanes.

Three pieces. (1) A cron entry that runs the curl-jq one-liner every 5 minutes and appends the seven_day_opus.utilization float to a CSV. (2) A weekly baseline script that correlates the CSV against a fixed corpus of prompts you care about, computing the server-delta-per-local-token ratio. (3) A threshold alert when the ratio jumps more than, say, 15 percent week-over-week, which is larger than any natural variance you will see from prompt mix alone. Every piece runs locally; the bridge is the data source. The ClaudeMeter menu-bar app keeps the snapshots fresh so the cron does not have to authenticate with claude.ai itself.

Two files, short enough to read in ten minutes. extension/background.js (~120 lines) has fetchSnapshots at line 14, which fetches the three account endpoints (/usage, /overage_spend_limit, /subscription_details) and posts them to BRIDGE = http://127.0.0.1:63762/snapshots defined at line 2. src/api.rs (~142 lines) has fetch_usage_snapshot which does the same thing from the macOS menu-bar process using a cookie-stealing path from Chrome's keychain. Both deserialize into the UsageResponse struct at src/models.rs line 19, so the shape on the bridge is identical regardless of which process wrote it.