AppRising

ccusage

App : A product you use directly

Reads local Claude Code logs and displays cost by day, session or model.

The first tool to install when paying for Claude Code on a usage basis.

GitHub · 19,167 ★

Overall score

8.9 /10

Security: nothing to flag

Utility

8.0

Reliability

10.0

Security

No caveat on record

Ease

5 min · Comfortable

Security reflects where data goes, requested permissions and incidents on record at the verification date. It is not a guarantee of zero risk: check the deployment mode and the connections you enable.

What it does, concretely

When using a coding agent like Claude Code on a pay-per-use basis, it is hard to know how much you are actually spending: tokens accumulate session after session with no overall view. ccusage solves this problem by reading the log files stored locally by these tools and producing clear cost reports.

The tool works entirely locally: it does not send any data to an external server. It analyses the log files of agents installed on the machine and displays summary tables by day, week, month or session, with a breakdown of tokens consumed and their cost in dollars.

ccusage supports a wide list of coding agents: Claude Code, Codex, Gemini CLI, GitHub Copilot CLI, Goose, Amp, Qwen, Grok Build CLI and many others. A single report can aggregate all agents detected on the machine.

This tool is aimed at developers who use one or more command-line coding agents and want to keep their spending under control. It is not suited to teams looking for a centralised solution: for that, the sponsor Lineman.io offers a dedicated product.

What it offers

·Usage reports by day, week, month or session for all agents detected on the machine.
·Support for more than 18 command-line coding agents, including Claude Code, Codex, Gemini CLI and GitHub Copilot CLI.
·Tracking of Claude Code's 5-hour billing windows via the blocks command.
·Per-model token breakdown, with detailed model-level cost breakdown available via the --breakdown flag.
·Data export in JSON format with the --json option for integration into other tools.
·Report filtering by date range (--since, --until) or recent period (--last 1).
·Offline mode (--offline) using cached pricing data, without a network connection.
·Integration into the Claude Code status bar via the statusline command (beta).

Our tips

Use --last 1 with daily, weekly or monthly to display only the current period without having to enter dates.
The --compact option forces a condensed table layout, handy for taking screenshots or sharing a report.
Combining --by-agent with --json produces a structured export that separates each agent's consumption, useful for analysing data in a spreadsheet.
For Claude Code, the command ccusage claude daily --instances groups usage by project, making it easy to identify which project consumes the most.
If you are working without an internet connection, add --offline so the tool uses cached pricing data and avoids any price-fetching errors.

Watch out

The tool only reads logs stored locally: if an agent does not keep log files on the machine, ccusage will not be able to measure its consumption.
The statusline command for the Claude Code status bar is still in beta and may exhibit unstable behaviour.

In practice

Price: Free
Commercial use: Commercial use: yes
Available on: cli
Licence: MIT

Security and data

Rating: Security: nothing to flag
Your data: Data stays local
Maintenance: Active
Last release: 24 October 2026

Links and repository checked on 25 October 2026 · added on 1 May 2025

How to install ccusage

1. Make sure Node.js is installed on your machine (required for npx). 2. No global installation is needed: the tool runs directly via a package runner. 3. Run the command npx ccusage@latest in your terminal to get the default report. 4. For faster repeated runs, prefer bunx ccusage, which caches the package after the first download. 5. Data stays on your machine: no information is sent to an external server.

npx ccusage@latest

In the same category

Whole category Route & save →