创建

登录 ReadmeX

或

了解我们如何处理你的信息: 隐私政策

ReadmeX

陪你读懂 AI 动态

今天,想先了解什么?

选一份动态总结,或直接聊聊你的问题。

社区和关注动态总结只属于你自己。

资讯

LangSmith上线编码智能体成果成本追踪公测

AI 总结

LangChain表示,LangSmith for Coding Agents现已在LangSmith Cloud开放公测,可将智能体追踪与支出关联到GitHub拉取请求和GitLab合并请求。新版总览仪表板按拉取请求、工作类型、模型及请求状态汇总成本,并将未产生拉取请求的工作记为未归因支出。该功能支持Claude Code、OpenAI Codex、Cursor、VS Code中的GitHub Copilot及Deep Agents。

深度见解

此次发布为工程和财务团队提供了统一的编码智能体成本与交付成果视图,但LangChain关于提升投资回报率的说法尚未得到独立验证。

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

原文约 7 分钟读完阅读原文
群聊

还没有评论,来说说你的看法。