Home / Problems / Track Claude Code costs and token use

Workflow problem

Track Claude Code costs and token use

Claude Code usage is hard to budget when work spans projects, sessions and models. Start with the built-in view, then inspect local history if you need trends.

The problem

Claude Code usage is hard to budget when work spans projects, sessions and models. Start with the built-in view, then inspect local history if you need trends.

Native approach

Run `/usage` (alias `/cost`) inside Claude Code to see the current session’s estimated cost, plan usage limits and activity stats. The session dollar figure is a local estimate; check the Claude Console or your plan page for billing.

Official Claude Code documentation ↗

Tools to consider

Local transcript analyzers estimate spend from recorded token use; treat provider billing as the source of truth.

FAQ

Does `/usage` break down spend by project?

No. Its session cost covers the current session; use a history analyzer for per-project trends.

Are local cost estimates invoices?

No. Pricing, caching and plan rules can differ from a local estimate.