LangWatch
Track Claude Code sessions, model calls, and token costs across devices
About LangWatch
LangWatch records each session as a trace through Claude Code's native OpenTelemetry export, covering model turns, tool calls, token types, and theoretical cost. Compared with ccusage-style local log readers, its OpenTelemetry route follows usage across devices and retains history after local log cleanup. The system automatically redacts API keys and personal information; individual users can use it for free, or pay by sent event and choose self-hosting.
Best for
Best use cases
View Claude Code session history across devices
Analyze model turns, tool calls, and token usage
Estimate the theoretical API cost of sessions
Retain tracking records after local log cleanup
Compare before choosing
The official comparison page says ccusage-style local log readers can see only one machine; the OpenTelemetry route tracks across devices and retains records after local log cleanup.
Features
Native OpenTelemetry integration
Sends each session to LangWatch through Claude Code's native OpenTelemetry export.
Complete session trace
Records model turns, tool calls, token types, and theoretical cost.
Cross-device tracking
The OpenTelemetry route follows usage across devices and retains records after local log cleanup.
Sensitive data redaction
Automatically redacts API keys and personal information so they do not enter the trace.
Pros
- Fully records model turns, tool calls, and token categories
- Tracking continues across devices and is unaffected by local log cleanup
- Automatically redacts API keys and personal information
- Free for individual users
Cons
- Subscription session costs are theoretical totals calculated at API list prices, not per-token invoices
Pricing Plans
Core seat
- Billing by sent event
* Pricing information is for reference only. Please refer to the latest announcement on LangWatch's official website.