Brain · Output

Output

See which model is worth its bill - per thousand output tokens. A per-model rollup of unit economics from your Claude Code telemetry: cost per 1k output tokens, share of output, share of cost, sessions. The answer to “is the more expensive model worth it for this kind of work?”

See it in motion

Where to find it

  • Localhost: /quality-output.html?repo=<id>
  • API: GET /api/quality/output?repo=<id>&period=<days>
  • Keyboard: ⌘ K then output
  • Sidebar: Insights → Coaching → Output

What it does for you

Compare models on the only number that matters: $ per 1k output.A sortable table with one row per model - sessions, output tokens, cost, $ / 1k out, output share, cost share. The amber bars (output share) vs rose bars (cost share) tell you instantly whether a model is over- or under-earning its keep.
Period picker keeps the comparison fair.7 / 30 / 90 / 365 day windows. A model that was great two months ago but is now a rounding error stops dominating the “all time” view.
By-language attribution is the next mile.Today the rollup is per-model. By-language (“Sonnet is great for TypeScript, Haiku for prose”) is deferred because cc-telemetry persists tool-use counts, not file_path arrays - a richer parser unlocks it. The page shows an explicit empty state so you know what's coming.

Configure

Period picker on the page. No other knobs - the data is pulled from cc.aggregate and analyzed by the pure lib/output-analysis.mjs module (tested, deterministic).

Use it well

Open Output before the next routing-tier decision. If a high-tier model has >50% of your spend but <50% of your output, you're probably over-routing. The LLM routing control tab is where you fix it - Output is where you decide what to fix.

Read more