Which coding (agent) CLIs and sources can ccusage analyze?

Updated

ccusage is a usage analysis tool for coding (agent) CLIs. Its default view is designed to show usage from all detected supported sources at once, rather than requiring you to pick a single tool first. The site also references Local Data Sources, which indicates that ccusage reads usage data already present on your machine instead of pulling it from a remote account dashboard. The exact list of supported CLIs is defined by the site's own documentation, so treat the categories below as the way ccusage organizes analysis, not as a fixed roster.

How ccusage decides what to analyze

The tool's behavior follows a detection-then-display model:

  1. Detection — ccusage looks for supported coding (agent) CLI data on the local system.
  2. Aggregation — by default, everything detected is combined into one view ("All Sources by Default").
  3. Focused views — you can narrow the output to a specific source when you don't want the combined picture.
  4. Cost analysis — usage is paired with cost-oriented reporting.
  5. Enhanced display — output formatting is treated as a distinct feature area.

The practical consequence: if a CLI isn't detected locally, it won't appear in the default view, even if ccusage conceptually supports that kind of source.

What "sources" means here

Layer What it refers to Why it matters
Coding (agent) CLI The command-line coding tool or agent that generated usage Determines which tools can appear in analysis
Local data source The on-disk usage records ccusage reads Explains why results depend on your machine's state
Default view All detected supported sources combined Gives a total picture without manual selection
Focused view A single source isolated Useful for per-tool cost or volume checks

How to confirm which sources you actually have

Because support is defined by the site and detection is local, the reliable check is to run ccusage and read what it reports:

  • If the default view lists a source, ccusage detected it locally.
  • If a tool you use is missing, the likely causes are: no local usage data, data stored in a location ccusage doesn't scan, or the tool not being in the supported set.
  • Use focused views to verify a single source is being read correctly before trusting an aggregate number.

Choosing how to use it

  • Use the default view when you want a single combined usage and cost picture across every detected coding CLI.
  • Use focused views when you need to attribute usage or cost to one specific tool, or when an aggregate looks wrong and you want to isolate the cause.
  • Check local data first if results seem incomplete — ccusage can only analyze sources it can detect on the machine.

For the authoritative supported-source list and any setup requirements, consult ccusage's own documentation, since the tool's coverage is defined there rather than by assumption.