UsagePace

A local pacing proxy for Claude Code’s weekly usage cap. Projects whether you’ll blow the cap before it resets, the question the built-in usage meter doesn’t answer.

The problem it solves

Claude Code shows you percentage of cap used. It doesn’t show you where you’re trending. At 60% with four days left, that could be fine or it could be a problem, depending on how you’ve been working. UsagePace shows you the projection.

How it works

Reads the per-message usage logs Claude Code already writes to disk. Cost-weights by model (Opus counts roughly 5× Sonnet against the cap), aggregates over the window, and extrapolates to the reset date. No API key, no network access. All local.

Limitations

It’s a proxy. Anthropic’s real cap formula is unpublished. The weights are calibrated against observed behavior: useful for trend-watching, not precise enough to rely on if you’re right at the edge.

From the devlog

A tool to answer the question my usage meter wouldn't — the full write-up, including the postscript.