LLM-driven workflows often hide telemetry in JSON or separate tools; this repo surfaces that telemetry directly in your terminal so you can see model, usage, and git context without leaving your session. The key idea: turn Claude Code's status JSON into a live, configurable status line that fits both casual sessions and power-user terminals.
What Sets It Apart
- Rich widget ecosystem with real metrics: model name, input/output/cached token counts, session/weekly usage, input/output/total token speeds, block timer, git insertions/deletions, and more — so you get live telemetry relevant to cost and context at a glance.
- Powerline & theme-first rendering with TUI editor: built-in Powerline separators, multiple themes, and an interactive React/Ink configuration UI — so you can design multi-line, aligned layouts without editing JSON by hand.
- Pragmatic terminal features: clickable OSC8 link widget, Windows-specific fixes (UTF-8 piped output, path handling), and fast piped renderer for CI or IDE integration — so it works reliably across terminals and setups.
- Integrations and extensibility: custom command widget and documented ccusage integration (via npx) let you chain other tools or fetch usage metrics directly — so the status line can combine external logic with Claude Code session data.
Who It's For & Tradeoffs
Great fit if you run Claude Code CLI and want immediate visibility into model/context/cost while working in a terminal or IDE integrated terminal. It suits developers who prefer terminal-native UIs and want clickable links, per-widget customization, and quick installation via npx/bunx.
Look elsewhere if you don't use Claude Code (the tool reads Claude Code status JSON) or need a GUI dashboard with historical analytics — ccstatusline focuses on live, in-terminal presentation, not long-term metric storage or multi-user dashboards. It also requires Node/Bun to run and some terminals to support OSC8 and truecolor for full fidelity.
Where It Fits
Use ccstatusline as a lightweight in-terminal overlay for conversational coding sessions: add it to your Claude Code settings, pair with ccusage for richer cost telemetry, or embed it in CI/dev containers to surface session metadata. If you need per-team dashboards or long-term aggregation, pair it with a separate usage-collection service instead of relying on the status line alone.
