Latitude is an observability and quality platform for AI agents. It helps developers find and fix failure modes before they reach production.
Most tools give you logs. Latitude gives you issues: failure modes with states and evals attached.
This is the 7th launch from Latitude. View more
Latitude for Claude Code
Launching today
Trace every Claude Code session. See the full system prompt, every tool call, every subagent, and token cost per turn. One command to install, free, your traces stay in your account. Receive a weekly report with your stats.
Free
Launch tags:Developer Tools
Launch Team / Built With
Latitude
Hey everyone,
It's Cesar, founder of Latitude.
If you keep hitting your Claude Code limits faster than you'd expect, this shows you why. Full session trace: system prompt, every tool call, subagent spawns, per-turn token cost. You see where your context actually went and which actions burn the most.
Same thing works if you're using Claude Code as a harness for your own agent: track cost and latency per session, and get recurring failures auto-flagged across runs.
Install is one command:
It's free, traces stay in your Latitude account.
Happy to answer technical questions in the thread.
LayerProof
this is genuinely what we need, especially being able to spot which sessions burn way more tokens than others lol.
Does this support the Claude Team plan, or API-only for now?
Latitude
@nathan_tran2 both are supported!
Does it work for Claude Cowork projects? I mainly burn my limits on Cowork sessions.
Latitude
@michael_vavilov We only support Claude Code at the moment. But if you want to hit your limits less, I suggest you to try Claude Code. It's not that different from Cowork and it can do the same things without spending as many tokens.
Does the recurring failure detection use heuristics, or are you applying some ML based pattern analysis?
Latitude
@xavier_hernandez2 Both
Token-burn observability for Claude Code is the kind of thing you only think to build after you blow a session on a regex loop. Curious how you handle the per-tool breakdown when an agent calls bash ten times for the same file read. Is it parsed from stream events or from the response after the fact?
congratulations, how much overhead does telemetry collection add to latency during active sessions?
Latitude
@olivia_bennett7 It adds no overhead at all. Telemetry data is sent asynchronously and adds no latency to runtime sessions.
Build Check
Oh man! Needed it. Claude is making me crazy, cause I never know where my tokens go. Thanks for helping on this and wish you all the best here!