Claude Pace

Know your quota before you hit the wall. A statusline for Claude Code — single Bash file, zero npm.

Most statuslines show "you used 60%." That number means nothing without context. 60% with 30 minutes left? Fine, the window resets soon. 60% with 4 hours left? You're about to hit the wall. claude-pace compares your usage rate to the time remaining and shows the delta. No Node.js, no npm, no lock files. Single Bash file.

• ⇣15% green = you've used 15% less than expected. Headroom. Keep going.
• ⇡15% red = you're burning 15% faster than sustainable. Slow down.
• 15% / 20% = used in the 5h and 7d windows. 3h = resets in 3 hours.
• Top line: model, effort, project (branch), 3f +24 -7 = git diff stats

Install

Requires jq.

Plugin (recommended):

Inside Claude Code:

/plugin marketplace add Astro-Han/claude-pace
/plugin install claude-pace
/reload-plugins
/claude-pace:setup

npx:

npx claude-pace

Restart Claude Code. Done.

Manual:

curl -o ~/.claude/statusline.sh \
  https://raw.githubusercontent.com/Astro-Han/claude-pace/main/claude-pace.sh
chmod +x ~/.claude/statusline.sh

Add to ~/.claude/settings.json:

{
  "statusLine": {
    "type": "command",
    "command": "~/.claude/statusline.sh"
  }
}

Restart Claude Code. Done.

To remove: delete the statusLine block from ~/.claude/settings.json.

Upgrade

• Plugin: /claude-pace:setup (pulls the latest from GitHub)
• npx: npx claude-pace@latest
• Manual: Re-run the curl command above.

Release notifications: Watch this repo → Custom → Releases.

How It Compares

	claude-pace	Node.js/TypeScript statuslines	Rust/Go statuslines
Runtime	jq	Node.js 18+ / npm	Compiled binary
Codebase	Single file	1000+ lines + node_modules	Compiled, not inspectable
Execution	~10ms, 3% of refresh cycle	~90ms, 30% of refresh cycle	~5ms (est.)
Memory	~2 MB	~57 MB	~3 MB (est.)
Failure modes	Read-only, worst case prints "Claude"	Runtime dependency, package manager	Generally stable
Pace tracking	Usage rate vs time remaining	Trend-only or none	None

Execution and memory measured on Apple Silicon, 300 runs, same stdin JSON. Rust/Go values are estimates.

Need themes, powerline aesthetics, or TUI config? Try ccstatusline. The entire source of claude-pace is one file. Read it.

Under the Hood

Claude Code polls the statusline every ~300ms:

Data	Source	Cache
Model, context, cost	stdin JSON (single jq call)	None needed
Quota (5h, 7d, pace)	stdin rate_limits (CC >= 2.1.80)	None needed (real-time)
Quota fallback	Anthropic Usage API (CC < 2.1.80)	Private cache dir, 300s TTL, async background refresh
Git branch + diff	git commands	Private cache dir, 5s TTL

On Claude Code >= 2.1.80, usage data comes directly from stdin. No network calls. On older versions, it falls back to the Usage API in a background subshell so the statusline never blocks.

Cache files live in a private per-user directory ($XDG_RUNTIME_DIR/claude-pace or ~/.cache/claude-pace, mode 700). All cache reads are validated before use. No files are ever written to shared /tmp.

Also by the Author

diffpane - Real-time TUI diff viewer for AI coding agents. See what Claude Code changes as it happens.

License

MIT