LangSmith Adds Outcome-Based Cost Tracking for Coding Agents
LangChain says LangSmith for Coding Agents is now available in public beta on LangSmith Cloud, linking agent traces and spend to GitHub pull requests and GitLab merge requests. A new overview dashboard aggregates costs by pull request, work type, model, and pull request state, while tracking work that does not produce a pull request as unattributed spend. The release supports Claude Code, OpenAI Codex, Cursor, GitHub Copilot in VS Code, and Deep Agents.
The release gives engineering and finance teams a shared view of coding-agent costs and shipped-code outcomes, although LangChain's claims about improving return on investment remain unverified.
Key Takeaways
- Increase the ROI of your coding agent spend by tracking and measuring outcomes, like pull requests, for your coding agents.
- A new concept called outcomes links GitHub pull requests or GitLab merge requests to threads, so you can see what a merged PR cost and how much spend never led to one.
- Every PR links back to the threads behind it, so you can investigate what's driving agent cost and how changes impact it.
Coding is the largest category of enterprise AI application spend, reaching $34B in 2026. Every company now wants to know what all that spend returns, but most engineering leaders still can’t give an exact answer to what it's buying.
To try to understand coding agent ROI, teams used to look at high-level data like usage analytics and AI consumption, but these don’t provide insight into what tokens actually produce. Answering the ROI question is hard and requires visibility into spend across users and teams, along with a way to connect it to outcomes. We felt this friction firsthand when spend with our own coding agent, Robin, started climbing, and is one of the reasons we built a model router.
#LangSmith#LangSmith for Coding Agents#Claude Code#OpenAI Codex#Cursor#GitHub Copilot#Deep Agents#GitHub#GitLab