What is ccusage and what does it do?

Updated

ccusage is a usage analysis tool for coding (agent) CLIs. It reads usage data from the coding CLI tools you already run and turns it into a consolidated view, so you can see how much you're actually using across supported sources instead of checking each tool separately. It's relevant if you use one or more coding agent CLIs and want a clearer picture of your activity and associated costs.

What problem it solves

Coding agent CLIs tend to keep their own usage records in their own formats and locations. If you use more than one, or want to understand cost rather than just raw activity, you end up piecing things together manually. ccusage aggregates that data into a single analysis view.

Core capabilities

Based on the site's own section headings, ccusage organizes its functionality around these areas:

Capability What it covers
All Sources by Default Views usage from all detected supported coding (agent) CLI sources at once
Focused Views Narrow the analysis to specific sources or slices rather than everything
Local Data Sources Works from usage data available locally on your machine
Cost Analysis Translates usage into cost figures
Enhanced Display Presents the analysis in a more readable/expanded form

All Sources by Default

The default behavior is aggregation: rather than asking you to pick a source first, ccusage detects supported coding (agent) CLIs and reports their usage together. This is the fastest way to get an overall picture.

Focused Views

When the aggregate is too broad, focused views let you isolate what you care about — for example, a single CLI or a specific subset of usage.

Local Data Sources

ccusage draws on local data sources, meaning the analysis is based on usage records present on your own system rather than a remote account dashboard.

Cost Analysis

Beyond counting usage, ccusage includes cost analysis, which is the piece most relevant if your concern is spend rather than volume.

Enhanced Display

An enhanced display mode presents the results in a more detailed or readable format than a bare summary.

Who it's for

  • Developers running one or more coding agent CLIs who want a single consolidated usage view.
  • Anyone trying to understand the cost side of their coding CLI usage, not just activity counts.
  • Users who prefer analyzing local usage data rather than logging into separate provider dashboards.

What to check before relying on it

  • Supported sources: ccusage only aggregates sources it detects as supported. If your CLI isn't among them, it won't appear in the default view.
  • Data availability: because it works from local data sources, the analysis is only as complete as the usage records your tools keep locally.
  • Cost accuracy: cost analysis depends on the usage data and pricing assumptions behind it; treat the figures as an analysis aid rather than a billing statement.

The site itself is the authoritative reference for the current list of supported sources and the exact commands or views available.