Which limit comes next?
5h, weekly, and model-scoped allowances stay separate. Each shows its usage and reset time, even while you inspect history.
ccpace
Your Claude usage, across the week.
A 5h limit can run out while the weekly pool goes unused. See both in one terminal calendar, with history, forecasts, and alerts.
uvx ccpace --calendar --demoNo account needed for the demo. macOS + Linux.
THE WEEK AT A GLANCE
Synthetic usage, rendered by ccpace. The amber line is 5h pressure; the weekly forecast remains visible beneath it.
Where did the week go?
Browse interval totals and hourly patterns. Select a day for the underlying observations. Missing history stays blank.
How much will remain?
Forecasts learn from your own weekday and hourly usage. Alerts can go to your terminal, phone, or a JSON notification hook.
GET STARTED
Open your calendar.
Install uv, then run the demo. For live usage, sign into Claude Code first.
# Synthetic demo, no credentials
uvx ccpace --calendar --demo
# Your Claude accounts
uvx ccpace --calendar
# A compact view, anytime
uvx ccpaceMeasured usage. Estimated forecasts.
Usage comes from the OAuth endpoints Claude Code uses. History and caches are shared with claude-code-statusline on your machine. Forecasts use that history; they are not promises of available capacity.
ccpace watches and warns. It does not control agent execution. Provider endpoints can change. Expired OAuth tokens are refreshed and written back; usage data stays local unless you configure notification destinations.
Data and limits ↗