简体中文
EnglishIs ccusage right for me and where should I start on ccusage.com?
Updated
ccusage is a usage analysis tool for coding (agent) CLIs. It is aimed at developers who want to see how much they are using these CLI tools and what that usage costs. If you already run one or more supported coding (agent) CLIs and want a single place to review usage across them, ccusage is likely relevant to you. If you do not use any coding (agent) CLI, there is nothing for it to analyze.
The site is organized around a few clear entry points. Start with the default view, then narrow down based on what you care about.
Start with the default view
The site's default behavior is described as All Sources by Default: it shows usage from all detected supported coding (agent) CLI sources at once. This is the natural first stop, because it tells you what ccusage can see on your machine before you filter anything.
Use this view when you want a broad picture: which sources are detected, and how usage is distributed across them.
Pick a view based on your question
| If your question is… | Go to |
|---|---|
| What can ccusage analyze at all? | The list of supported coding (agent) CLIs and sources |
| How do I narrow the output to one tool or dimension? | Focused Views |
| What is this costing me? | Cost Analysis |
| Where does the data come from? | Local Data Sources |
| How is the output presented? | Enhanced Display |
Focused Views and Enhanced Display
Focused Views let you move past the all-sources default and look at a narrower slice of usage. Enhanced Display covers how results are presented rather than what is measured. Together these two sections answer "can I get the specific cut I want, and will it be readable?" — which is usually the deciding factor for whether a usage tool is worth adopting.
Cost Analysis
Cost Analysis is the section to check if spending is your main concern. It is where ccusage turns usage into cost figures. If you only care about raw usage counts, you can skip it; if you need to justify or track spend, start here after the default view.
Local Data Sources
Local Data Sources explains where ccusage gets its input. The name signals that analysis is based on data already present locally rather than a remote account dashboard. Read this section if data provenance matters to you — for example, if you need to know what has to be installed or run before any numbers appear.
A practical path through the site
- Read the top-level description to confirm ccusage targets coding (agent) CLIs.
- Check the supported sources list to confirm your CLI is covered.
- Run or review the default all-sources view to see what is detected.
- Move to Focused Views to isolate the tool or dimension you care about.
- If cost matters, go to Cost Analysis; if data origin matters, go to Local Data Sources.
What to verify before committing
- Coverage: confirm your specific coding (agent) CLI appears in the supported sources. Nothing else on the site matters if yours is not listed.
- Data availability: check Local Data Sources to understand what must exist locally for analysis to work.
- Output fit: skim Focused Views and Enhanced Display to confirm the cuts and presentation match how you actually want to read usage.
If all three check out, ccusage fits your workflow. If your CLI is unsupported or you have no local usage data to analyze, it is not the right tool for you.