Last week we announced our series C and introduced the new LangSmith Agent Platform: a single place to build, run, improve, and govern every agent. With this, agents are now the core object across LangSmith, connecting fragmented workflows for developers and enabling platform teams to manage agents across the business.
In this post, we discuss why we reorganized the product, how the agent model works, what it unlocks, and where we're taking it next.
Why did we rebuild LangSmith?
2026 brought a step change in agent adoption as new harnesses, models, and engineering approaches made it possible to build agents that can reliably perform complex, high value work.
Companies now run many agents across the business: engineering uses coding agents, product is building customer-facing agents, and teams across the organization have various internal productivity agents. These agents are built with different frameworks, hosted on various runtimes, and use a variety of tools and models.
The result is fragmented workflows for both engineers and platform teams.
Engineers work across disconnected surfaces. Tracing, monitoring, and deployments all live in different places. This requires frequent context switching, and in practice results in teams skipping difficult but important steps like building the evals.
AI Platform teams have difficulty answering basic governance questions. Which agents exist, and who owns each of them? What do they cost, and how are they performing? When costs spike, there is often no obvious person to ask what happened.
We wanted to make it simple for teams to manage the entire agent development lifecycle from one place, using any stack, with ownership and governance across all of it.
One platform for the entire agent development lifecycle
LangSmith supports the entire agent development lifecycle: build, run, improve, and govern. Now, we've connected the entire process through a unique agent record.
Build: Describe an agent with the new natural language builder in LangSmith Studio, build in code with our open source harnesses, or use any other framework.
Run: Deploy on LangSmith Agent Server or keep the agent on the runtime you already use.
Improve: Tracing, evals, datasets, annotation, and Engine work on any agent that sends traces to LangSmith.
Govern: LangSmith agent registry and LLM Gateway provide org-level visibility and strict controls over every registered agent.
When you open an agent record, its traces, evals, Agent Server, and Engine issues are accessible with one click, so you don’t need to navigate multiple surfaces to find them. Each agent’s local, dev, staging, and production environments sit under the same agent ID, so comparing performance after making changes is simple.