Repository navigation
v0.2.0
cc-pace still answers one question - am I burning my usage too fast? - and now says why, and what to do about it. Still zero tokens, zero API calls, zero dependencies.
New on the line
- Recent burn warning -
Weekly 1h7m to 100% (22:13). The window average hides a hard hour after a quiet week; this measures the last hour and speaks only when it hits 100% before the reset. - Why it burns - over budget, the model, its settings and each model's share of the spend follow the ratio:
Opus 5.5/medium 71% · Sonnet 5.5 27%, subagents included, priced to match/usage. - Cache warning -
cache cold in 12m (270k). After a break the next turn re-sends the whole conversation;/compactfirst avoids it. - Memory - how full this conversation is (what
/compactclears). - This chat - this session's share of what all open sessions spent in the last hour.
! configwhen the config file cannot be read, rather than silently ignoring it.
With cc-account
cc-pace works alone. Installed with cc-account it also switches accounts by itself: it skips logins about to stop refreshing, drains the account whose weekly reset would waste the most quota first, and forecasts whether the accounts together last - Pool: 1.40x/2.0x ok.
Changes
--setupaddsrefreshInterval: 60, so the line keeps time while you are idle.- Windows limited to one model (Opus, Sonnet, Fable, any future one) are hidden unless
showModelWindowsis on. - The pace ratio appears once 5% of a window has elapsed (was 2%), so it no longer swings at the start of a week.
- Labels use your terminal's own colour; grey is kept for the secondary parts.
git statusruns with--no-optional-locks, so it never takesindex.lockfrom under Claude Code.