Track Claude Code Token Usage and Cost

Quick answer

If you want per-turn token and dollar breakdowns while you code, you have four realistic options today:

Tool	What it shows	Best for
`/usage` in Claude Code	Session totals in the terminal	Quick glance at current session
ccusage	CLI rollup from local JSONL	Power users who want terminal reports
Anthropic Console	Org-wide API usage	Billing admins, not per-repo context
PromptConduit	Live status bar + per-prompt cost in the editor, local JSONL capture, optional cloud history	Developers who want cost in the loop

PromptConduit prices every turn against public API rates so you see what the same tokens would cost on pay-as-you-go — including cache read/write splits — without waiting for a dashboard export.

Why `/usage` isn’t enough

Claude Code’s built-in /usage command is useful for a single-session total. It does not:

Break down which prompts drove spend
Show cache read vs fresh input per turn
Roll up across sessions or by repository
Compare what another model would have cost for the same token counts

For a 45-minute refactor with twenty subagent calls, you still wonder which three prompts ate half the budget.

ccusage vs PromptConduit

ccusage reads the same ~/.claude/projects/ JSONL files and prints terminal summaries. It’s excellent if you live in the shell.

PromptConduit targets a different moment: before you send the next prompt. The editor extension streams promptconduit cost watch into a status bar and a click-through panel — totals, per-model rows, and per-request detail without leaving Cursor or VS Code.

Both are local-first. Neither uploads your transcripts unless you opt into cloud sync.

Anthropic dashboard gaps

The Anthropic Console shows API usage for keys under your org. That’s the right place to reconcile invoices.

It won’t tell you:

Which git repo a spike came from
Which Claude Code session (vs a script or CI job) spent it
How permission mode or subagents changed the curve mid-session

PromptConduit enriches each event with git context (repo_name, branch) at capture time via the CLI hook.

Get started locally (no account)

curl -fsSL https://promptconduit.dev/install | bash
promptconduit install claude-code
promptconduit install cursor   # optional — same cost panel for Cursor

Install the PromptConduit editor extension for live cost in the status bar.

Everything stays on disk in ~/.promptconduit/events.jsonl until you run promptconduit login and sync.

When to add Pro or Team

Pro ($10/mo) — 90-day cloud history, weekly digest, cross-machine skill library
Team ($15/seat/mo) — shared rollups across members, repos, and models

See pricing for the full tier comparison.