Claude Code usage tracking by LangWatch - See what your Claude Code sessions actually cost

by
Track Claude Code usage: cost, cache, session replay. Run `npx langwatch claude` once. Every session gets cost with cache reads/writes as separate token classes, every bash and MCP call as a span, theoretical vs billed for your Max plan, and a full terminal replay in the UI. Works for Codex too.

Add a comment

Replies

Best

The combination of cost tracking, session replay, and tool tracing makes this much more than another analytics dashboard. Congrats on launching!!!

 that's right! LangWatch is currently the most powerfull observability tool for it! But I might be a bit bias! ;)

Knowing exactly what each Claude Code session costs is a game changer. Congrats on the launch, this is awesome! 🚀

 thanks, this is just the beginning!

 thanks 🙏 let us know once you’ve tried

This is such a killer feature for heavy users and big teams with distributed sessions leveraging multiple providers! Great work, !

great product! knowing the per-seat cost but not which sessions burned is a proper problem, especially as the costs keep rising. this is going to save me from getting broke!

 hope ai coding solutions will also bring your team / product / company the speed and competitie advantage to win the game and get more revenue in ,! But we’ll def be there to nbe more efficient

really proud of this launch!

the MCP tool calls as spans is the bit i want most. i drive a browser automation MCP from claude code all day and the screenshots are obviously the expensive part, except obviously is doing a lot of work in that sentence because i have no per-call number for any of it.

cache reads and writes counted separately is the other one, that is where the surprise usually hides.

 yeeppp both are in there: every MCP call gets its own span with its own token cost, and cache reads and writes are broken out separately, so you'll have a real per-screenshot number instead of a hunch.

Watching an entire terminal session replay sounds surprisingly valuable for onboarding teammates.

 interesting use-case!

Can the platform can identify inefficient prompting patterns across multiple sessions?

It would be interesting if LangWatch suggested ways to reduce costs based on previous usage.

 That's exactly where we're headed, this is the groundwork for it, so what kinds of suggestions would actually be useful to you?

Congrats on shipping this! Finally a way to know exactly how much those late-night Claude Code sessions are costing me. My wallet thanks you already!

 haha very welcome!