Purpose
claude-pace is aimed at developers using Claude Code, for monitoring account quota consumption in real time in the status bar. It specifically solves the problem of "showing only the used percentage, without time context": for example, if 60% is used, that is fine if only 30 minutes remain in the window, but if 4 hours remain, you may be about to hit the cap.
Main capabilities
- Display quota usage percentages for the 5-hour and 7-day windows in the Claude Code status bar.
- Display the reset countdown for each window (e.g. 3h).
- Pace-aware: compare the current burn rate with the proportion of elapsed time in the window, and output the pace difference. ⇣15% in green means 15% less usage than expected (there is headroom); ⇡15% in red means burning 15% faster than the sustainable rate (you need to slow down).
- The top line shows the model, effort, project (branch), and git diff stats (e.g. 3f +24 -7).
- Reads the rate_limits field from the Claude Code 2.1.80+ status bar stdin; if that field is missing (older versions or providers that do not supply it), the 5h/7d quota displays --, session cost is displayed if available, and stale cached quota is not displayed.
- The git cache file is stored in a user-private directory ($XDG_RUNTIME_DIR/claude-pace or ~/.cache/claude-pace, permissions 700), is validated before reading, and is not written to shared /tmp.
Usage
It can be installed inside Claude Code via a plugin (recommended), using the /plugin marketplace add and /plugin install commands and then restarting; it can also be run with npx claude-pace@latest; or manually by adding a statusLine configuration in ~/.claude/settings.json. To remove it, just delete that statusLine block. Updates: for the plugin, use /plugin marketplace update and /plugin update; for npx, just run it again; for manual installation, rerun the curl command. All channels install a tagged release version, not from main.
Applicable scenarios and limitations
It is suitable for users who want fine-grained management of Claude Code quota and to avoid suddenly hitting the cap before the window ends, especiallyfor long coding sessions where you need to judge whether you can keep going. The tool itself does not make network requests; quota data comes entirely from stdin. Running it requires jq (installable via brew install jq or a package manager) and does not require Node.js. Execution and memory data are measured on Apple Silicon, with 300 runs, using the same stdin JSON. If you need themes, powerline styling, or TUI configuration, consider ccstatusline. The source code is a single Bash file that you can review yourself.