Skip to content

Releases: O0000-code/cc-tempo

v0.1.0 — Initial Release

18 Apr 07:56

Choose a tag to compare

A Claude Code statusline that measures real work time, SubAgent speedup, and code-churn pace — not just tokens and cost.

49.7M tokens · $29.46 | Context: ████████████░░░░░░░░ 60% | Cached 85% · ⏱ 2h 15m [1.8×]
───
main · 2 active | +156 -23 · 12 files · 89 lines/$ | Quality: ▁▁▂▃▅▆▇█ ↑
───
Limits: 5h ▮▮▮▮▮▮▮▮▯▯ 87% · 7d ▮▮▮▮▮▮▮▯▯▯ 71% | ↻ 47m · 2d 3h

What makes it different

Five things set cc-tempo apart from the ~15 existing Claude Code statuslines on GitHub:

  • ⏱ 2h 15m Active work time — parsed turn-by-turn from the transcript JSONL. Excludes user-idle gaps and waits on interactive tools (AskUserQuestion, ExitPlanMode). Cumulative api_duration_ms inflates under parallel SubAgents; this doesn't.
  • [1.8×] Speedup ratio — API cumulative time ÷ active wall-clock time. Surfaces only when the ratio reaches 1.2, so when you see it, SubAgent parallelism is actually helping.
  • /clear-resilient timing — PID-keyed /tmp accumulator; /clear inside the same claude process does not reset the clock. A new claude invocation starts clean. claude --continue inherits the dead PID's accumulated total.
  • Quality: ▁▁▂▃▅▆▇█ ↑ Code-churn sparkline — 8-char velocity track of added+removed lines per tick, zero-separate + log₂ min-max normalized, with a trend arrow after three data points.
  • 2 active Multi-instance detection — surfaces concurrent claude processes on the same project directory.

Plus the table stakes: 20-char context bar, cache hit rate, lines-per-dollar efficiency, git diff stats, and 5h/7d rate-limit gauges with reset countdowns.

Install

git clone https://github.com/O0000-code/cc-tempo.git
cd cc-tempo
./install.sh

Prerequisites: jq, bc, python3 ≥ 3.8, Node.js ≥ 18, git. On macOS: brew install jq bc.

Links