Langsmith
LangChain’s evaluation and observability product for AI systems. The newsletter positions it as the measurement layer for an agent orchestration loop.
Key Highlights
- LangSmith is positioned as the measurement and observability layer for agentic AI systems in the LangChain ecosystem.
- Newsletter coverage ties LangSmith to traces, evaluator design, deep-agent debugging, and recursive improvement loops.
- Its Messages View helps teams replay conversations and tool calls from the agent’s perspective for faster debugging.
- Benchmarks cited in the newsletter suggest automated eval tools like LangSmith catch obvious failures but still miss product-judgment issues.
- LangSmith is increasingly presented as infrastructure for managed deep agents, sandboxed evaluations, and observability-driven learning.
Langsmith
Overview
LangSmith is LangChain’s evaluation, observability, and measurement product for AI systems. In the newsletter, it is repeatedly framed as the measurement layer around agent workflows: a system for tracing model and tool behavior, replaying executions, running evaluations, and supporting iterative improvement of agents and LLM-powered applications. Across mentions, it expands beyond simple logging into a broader platform that includes observability, sandboxed experimentation, deployment support, and infrastructure for managed deep-agent workflows.For AI Product Managers, LangSmith matters because it addresses one of the hardest problems in AI product development: knowing whether an agent or LLM system is actually getting better. The coverage positions it as a practical way to inspect traces, define evaluators, analyze failures, and connect product feedback to measurable improvement loops. In agent-heavy products, where failures often happen at the boundaries between prompts, tools, context, and recovery logic, LangSmith shows up as the system of record for measurement and debugging.
Key Developments
- 2026-06-01: Harrison Chase explained how to evaluate DeepAgents at scale on AWS with LangSmith, including concrete datapoint and evaluator design patterns for longer-horizon agents.
- 2026-06-04: LangSmith was presented with three core components: Sandbox for isolated prototyping, an LLM Gateway for unified model access, and Observability tools for end-to-end monitoring.
- 2026-06-29: Harbor was introduced as a LangChain/LangSmith integration for running sandboxed evaluations, with self-hosted sandboxes planned.
- 2026-07-12: LangSmith was described as offering cloud-based sandboxes and deployments, deep-agent orchestration, and observability tracing, with integrations across many LangChain-supported models and a role in recursive improvement.
- 2026-07-30: Openwiki was demoed as a memory-powered wiki that parses LangSmith traces from coding agents to automatically update documentation.
- 2026-08-09: Managed Deep Agents launched, combining a deep-agents harness with managed LangSmith infrastructure.
- 2026-08-15: New documentation introduced a mental model around traces, threads, and trajectories, highlighting how observability data can support memory and learning.
- 2026-08-24: Hamel’s benchmark found that LangSmith and similar automated-eval tools caught many obvious failures but still missed product-judgment failures; reported best-case precision was 80% to 90%.
- 2026-09-03: LangSmith’s Messages View was highlighted as a way to replay conversations and tool calls from the agent’s perspective, making traces more useful for builders, not just infra teams.
- 2026-09-10: Harrison Chase described an emerging loop with deepagents handling orchestration logic and LangSmith serving as the measurement layer for iterative agent improvement.
Relevance to AI PMs
1. Turn agent behavior into something measurable. LangSmith gives PMs a way to move from anecdotal bug reports to trace-backed evaluation. That helps teams define failure modes, compare versions, and decide whether a new prompt, tool policy, or context strategy actually improves outcomes.2. Improve debugging across product, engineering, and AI teams. Features like trace replay and Messages View make it easier to inspect what the agent saw, which tools it used, and where it failed. PMs can use this to speed up triage, reproduce issues, and align teams around concrete evidence rather than vague user complaints.
3. Support eval loops for longer-horizon agents. The newsletter repeatedly connects LangSmith to DeepAgents, harness design, and recursive improvement. For PMs shipping multi-step agents, LangSmith is relevant as the layer for evaluator design, experiment tracking, and measuring whether harness changes improve real task completion instead of just single-turn outputs.
Related
- LangChain: LangSmith is closely tied to the LangChain ecosystem and is positioned as its evaluation and observability layer.
- Harrison Chase: Frequently cited as the main spokesperson and product explainer for LangSmith’s roadmap and mental models.
- DeepAgents / managed-deep-agents: LangSmith appears as the measurement and managed infrastructure layer around deep-agent orchestration.
- Agent harnesses: The newsletter frames agent improvement as harness improvement, with LangSmith helping measure changes at the tool, context, and recovery layers.
- Traces, threads, trajectories: These concepts form the evolving mental model for understanding and learning from agent runs.
- LLM-as-a-judge / OpenAI Evals / PromptLayer Evaluations / Braintrust Loop / Arize Alex: These are adjacent evaluation approaches or competing/comparable tooling in the AI eval stack.
- Harbor: Connected as a LangChain/LangSmith integration for sandboxed evaluations.
- Openwiki: Uses LangSmith traces from coding agents to automatically update documentation, showing downstream product workflows built on observability data.
- AWS: Mentioned in the context of scaling DeepAgents evaluation with LangSmith.
Newsletter Mentions (19)
“He said a loop is being built around deepagents for orchestration logic and LangSmith for measurement.”
#8 𝕏 Harrison Chase endorsed the view that agent improvement is harness improvement, with key interventions at the tool boundary: context selection, tool availability, failure recovery, and measurement. He said a loop is being built around deepagents for orchestration logic and LangSmith for measurement.
“Harrison Chase shared that LangSmith’s Messages View helps builders debug agents by replaying conversations and tool calls as the agent experienced them, making traces useful beyond infrastructure teams.”
Harrison Chase shared that LangSmith’s Messages View helps builders debug agents by replaying conversations and tool calls as the agent experienced them, making traces useful beyond infrastructure teams.
“Hamel’s benchmark found automated-eval tools such as Braintrust Loop, Arize Alex, and LangSmith recovered many obvious failures but missed product-judgment failures such as unhandled sales objections; their best-case precision was stated as 80% to 90%, meaning 10% to 20% of flagged errors were not actual errors.”
#1 ▶️ How to Build Better AI Evals with Claude Code in 5 Steps | Shreya & Hamel Peter Yang Shreya uses the free Error Discovery Skill in Claude Code with Opus 4.8 to turn human feedback on AI-generated writing into annotated failure modes, an evaluation rubric, and reusable LLM-judge criteria. The Error Discovery Skill performs five steps: identifies the dataset’s semantic type, designs visual encoding, builds an HTML/Python review app, clusters data and selects diverse samples, then uses an interactive feedback loop to propose new samples and rubric criteria. In the live run, Claude took about 15 minutes to build a three-tab review interface with article-by-article, map/clustering, and progress views; after feedback was supplied, it generated 361 suggested annotations, including 249 instances of the “less than four words staccato” rule. Hamel’s benchmark found automated-eval tools such as Braintrust Loop, Arize Alex, and LangSmith recovered many obvious failures but missed product-judgment failures such as unhandled sales objections; their best-case precision was stated as 80% to 90%, meaning 10% to 20% of flagged errors were not actual errors.
“Harrison Chase shared new LangSmith documentation covering traces, threads, and trajectories—a new concept—and said observability data can support memory and learning, making a clear mental model especially helpful.”
#13 𝕏 Harrison Chase shared new LangSmith documentation covering traces, threads, and trajectories—a new concept—and said observability data can support memory and learning, making a clear mental model especially helpful.
“#3 𝕏 Harrison Chase shared a 20-minute explanation of Managed Deep Agents, which he said had launched the previous day and combines a deep agents harness with managed LangSmith infrastructure.”
GenAI PM Daily August 09, 2026 GenAI PM Daily 🎧 Listen to this brief 3 min listen Today's top 10 insights for PM Builders. Claude Code sessions can now message each other #3 𝕏 Harrison Chase shared a 20-minute explanation of Managed Deep Agents, which he said had launched the previous day and combines a deep agents harness with managed LangSmith infrastructure.
“Harrison Chase demos openwiki, a “dreaming” memory–powered wiki that runs scheduled background jobs to parse LangSmith traces of coding agents and automatically update your codebase documentation.”
#10 𝕏 Harrison Chase demos openwiki, a “dreaming” memory–powered wiki that runs scheduled background jobs to parse LangSmith traces of coding agents and automatically update your codebase documentation. #11 𝕏 Guillermo Rauch built a harness that adds vision capabilities to every AI model, enabling them to process and interpret images seamlessly.
“Harrison Chase launched LangSmith, offering cloud-based sandboxes & deployments, deep‐agent orchestration, and observability tracing. It integrates with hundreds of LangChain models and powers recursive improvement via the LangSmith engine.”
#7 𝕏 Harrison Chase launched LangSmith, offering cloud-based sandboxes & deployments, deep‐agent orchestration, and observability tracing. It integrates with hundreds of LangChain models and powers recursive improvement via the LangSmith engine.
“#4 𝕏 Harrison Chase announces Harbor, a LangChain/LangSmith integration for running sandboxed evaluations, with self-hosted sandboxes coming soon.”
The newsletter mentions Harbor as a LangChain/LangSmith integration aimed at sandboxed evaluations.
“#19 𝕏 Harrison Chase unveiled LangSmith with three core components—Sandbox for isolated prototyping, LLM Gateway for unified model access, and Observability tools for end-to-end monitoring.”
GenAI PM Daily June 04, 2026 GenAI PM Daily 🎧 Listen to this brief 3 min listen Today's top 25 insights for PM Builders, ranked by relevance from Blogs, X, YouTube, and LinkedIn. Google launches Gemma 4 12B for local multi-step reasoning #19 𝕏 Harrison Chase unveiled LangSmith with three core components—Sandbox for isolated prototyping, LLM Gateway for unified model access, and Observability tools for end-to-end monitoring.
“Harrison Chase breaks down how to evaluate DeepAgents at scale on AWS with LangSmith, covering concrete datapoint and evaluator design methods for longer-horizon agents.”
#2 𝕏 Harrison Chase breaks down how to evaluate DeepAgents at scale on AWS with LangSmith, covering concrete datapoint and evaluator design methods for longer-horizon agents.
Related
Founder and CEO of LangChain, known for agent and orchestration commentary. Here he argues that agent improvement depends on harness design, tool boundaries, and measurement.
A framework company for building LLM apps and agents. In this issue it is mentioned alongside Deep Agents and virtual file system infrastructure.
Autonomous or semi-autonomous AI systems that can plan and take actions across tools and workflows. This is a core AI PM concept central to product design and evaluation.
An orchestration layer or project for building agent loops and control logic. In this newsletter it is described as part of a loop for orchestration logic alongside LangSmith.
Agents used to write, review, and iterate on code as part of software development workflows. The newsletter frames them as shifting developers toward specification, architecture, and evaluation work.
Amazon’s cloud platform, referenced in a story about a training pipeline running on a 4-GPU instance. The anecdote highlights GPU utilization monitoring and infrastructure waste.
Stay updated on Langsmith
Get curated AI PM insights delivered daily — covering this and 1,000+ other sources.
Subscribe Free