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.
Hey Product Hunt, Manouk here, founder of LangWatch.
We built this because we run a fleet of coding agents ourselves and had no idea what they actually cost: subscriptions hide the number, and local trackers only see one machine.
You know what Claude Code costs you per seat. What you probably can't answer is which sessions burned the budget, which model did the work, or whether your cache was earning its keep. Today's token prices are heavily subsidised, and the teams who find out what they actually consume after prices move are the ones who get surprised.
This week we've added a new launch in LangWatch, which our dev-team is using day-in, day-out. You can now track your full Claude Code usage on LangWatch: every session, tokens spent throughout the month, cache hit analysis, bash commands, skills and MCP tool calls, with a full reproduction of your terminal right in the UI.
Getting started is one command:
npx langwatch claude
From there, every session lands in LangWatch automatically:
Where the tokens go: cost per session and per model, with cache reads and writes accounted separately.
Theoretical vs billed: on a Max plan, see what your usage would have cost at API prices.
Every tool call: bash commands, file edits, skills, and MCP calls, each as a span with duration.
Terminal replay: step through the whole session in the UI, as it happened.
Works the same for Codex, Gemini CLI, and opencode.
I'll be here all day, happy to answer anything, and genuinely curious what you'd want to see next in it.
About Claude Code usage tracking by LangWatch on Product Hunt
“See what your Claude Code sessions actually cost”
Claude Code usage tracking by LangWatch launched on Product Hunt on July 30th, 2026 and earned 304 upvotes and 78 comments, placing #4 on the daily leaderboard. 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.
On the analytics side, Claude Code usage tracking by LangWatch competes within Open Source, Developer Tools, Artificial Intelligence and GitHub — topics that collectively have 1.1M followers on Product Hunt. The dashboard above tracks how Claude Code usage tracking by LangWatch performed against the three products that launched closest to it on the same day.
Who hunted Claude Code usage tracking by LangWatch ?
Claude Code usage tracking by LangWatch was hunted by Rohan Chaubey. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Reviews
Claude Code usage tracking by LangWatch has received 4 reviews on Product Hunt with an average rating of 5.00/5. Read all reviews on Product Hunt.
For a complete overview of Claude Code usage tracking by LangWatch including community comment highlights and product details, visit the product overview.
Rohan Chaubey
Hey Product Hunt, Manouk here, founder of LangWatch.
We built this because we run a fleet of coding agents ourselves and had no idea what they actually cost: subscriptions hide the number, and local trackers only see one machine.
You know what Claude Code costs you per seat. What you probably can't answer is which sessions burned the budget, which model did the work, or whether your cache was earning its keep. Today's token prices are heavily subsidised, and the teams who find out what they actually consume after prices move are the ones who get surprised.
This week we've added a new launch in LangWatch, which our dev-team is using day-in, day-out. You can now track your full Claude Code usage on LangWatch: every session, tokens spent throughout the month, cache hit analysis, bash commands, skills and MCP tool calls, with a full reproduction of your terminal right in the UI.
Getting started is one command:
npx langwatch claude
From there, every session lands in LangWatch automatically:
Where the tokens go: cost per session and per model, with cache reads and writes accounted separately.
Theoretical vs billed: on a Max plan, see what your usage would have cost at API prices.
Every tool call: bash commands, file edits, skills, and MCP calls, each as a span with duration.
Terminal replay: step through the whole session in the UI, as it happened.
Works the same for Codex, Gemini CLI, and opencode.
Free for individual use.
Start tracking your own sessions
I'll be here all day, happy to answer anything, and genuinely curious what you'd want to see next in it.