Claude Code usage tracking by LangWatch

See what your Claude Code sessions actually cost

Developer ToolsArtificial IntelligenceGitHubOpen Source

▲ 175 votes47 commentsLaunched Jul 30, 2026

Visit Website

Daily #1Weekly #24

Claude Code usage tracking by LangWatch screenshot 1

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.

AI Analysis

📝 Summary

Claude Code usage tracking by LangWatch is a CLI tool for developers to monitor Claude (and Codex) coding sessions. Running `npx langwatch claude` once enables detailed cost tracking with cache reads/writes as separate token classes, spans for every bash and MCP call, comparison of theoretical vs billed costs for Max plans, and full terminal session replay via UI dashboard. It addresses key pain points like unpredictable API expenses, lack of usage transparency, and difficulty reviewing AI coding interactions. USP is zero-setup visibility into real costs and replays. Overall value proposition: empowers cost control, optimization, and debugging for AI-assisted coding workflows.

📈 Market Timing

Favorable in 2025-2026 due to surging adoption of AI coding agents and tools like Claude with computer use capabilities. LLM usage is maturing but costs are escalating, driving demand for precise observability. Tech for token tracking and session replay is ready, while economic pressures for AI ROI and dev efficiency create strong need. Excellent Timing.

✅ Feasibility

High. Low technical difficulty via npx/CLI wrapper for API monitoring; minimal dev and operation costs as lightweight tool. Low supply chain or compliance risks for usage analytics. Strong scalability to cloud UI and potential team fit for AI tooling developers. Main challenge is maintaining compatibility with evolving Claude APIs.

🎯 Target Market

Main segments: Software developers and AI engineers using Claude for coding (e.g. via terminal, IDEs). Industries: Tech/software dev, startups. Geographic: Global with concentration in US/Europe. LLM observability TAM is large and growing; core pain points are opaque costs and session opacity. Potential willingness to pay is high for teams seeking budget control, likely via freemium to paid plans.

⚔️ Competition

Medium. Direct competitors: 1. LangSmith (smith.langchain.com), 2. Langfuse (langfuse.com), 3. Helicone (helicone.ai), 4. Phoenix (arize.com/phoenix). Advantages: hyper-focused on Claude Code with unique terminal replay, cache-specific token classes, one-command install, and spans for bash/MCP. Disadvantages: narrower scope than full-stack observability platforms; less brand recognition; depends on LangWatch infrastructure.

Upgrade Pro to unlock full AI analysis