The Lab · AI Platform
Managed Deep Agents
LangSmith's hosted runtime for Deep Agents, deployed by a single CLI command
Managed Deep Agents turns a folder of markdown instructions into a hosted, traced agent endpoint, which removes the hosting chore that usually strands agents in a notebook.
The verdict
The draw here is subtraction: the Deep Agents harness, the Agent Server API and tracing all come off your to-do list, so a working prototype can go live without a separate hosting project. LangChain developers with a Deep Agents build should run it on an internal workload now. Customer-facing agents can wait until the beta label comes off and the managed runtime's billing is clear.
- Good for
- LangChain developers with Deep Agents prototypes; Teams shipping internal Slack agents
- Skip it if
- Teams that need full runtime control; Shops outside the LangChain stack
- Costs
- No price found1
What it does
As Managed Deep Agents describes it.1
- Project-folder deploy
- Treats a project directory as the agent definition and pushes it to hosted LangSmith infrastructure with one CLI command.
- Deep Agents harness
- Runs LangChain's Deep Agents harness, which plans and calls tools across multi-step tasks.
- Agent Server API
- Exposes each deployed agent through LangSmith's Agent Server API so other apps can call it.
- Built-in tracing
- Records every live run in LangSmith so you can inspect what the agent did step by step.
- Bundled web search
- Gives agents Parallel web search without opening a separate vendor account or managing another API key.
Ways to put it to work
Ship-the-notebook test · for the LangChain developer with a working prototype
Move the prototype's prompts and tools into a project directory, deploy it, then send a handful of real tasks to its Agent Server API while the traces stream in.
You get: A quick read on whether the agent behaves the same hosted as it did locally, with no infrastructure built.
Slack thread assistant · for the internal tools team
Wire an existing Deep Agent into Slack so colleagues can invoke it in channels or inside threads, and review each conversation in LangSmith afterward.
You get: An agent people actually use at work, with a record of every run for debugging.
Managed or self-hosted rule · for the platform lead
Keep an agent on the managed service while its harness defaults fit; the first time you need a runtime knob it does not expose, move that agent to the Deep Agents SDK.
You get: A clear trigger for migration, and because the harness is shared the move only changes where it runs.
What it costs
No price found1
Our take: The LangSmith pages read showed no price for Managed Deep Agents, so ask LangChain how beta usage is billed before you route production traffic to it.
What people say
Independent reaction is still thin: one puzzled Reddit thread and one upbeat LinkedIn post make up most of the commentary so far.
After watching LangChain's video on Managed Deep Agents, a user said it looked so similar to Deep Agents that they could not see why both need to exist.
A developer called it sneaky cool, saying you can build and ship agents using only markdown files and one line of code.
Where it falls short
- Still a public beta on LangSmith Cloud and Bring Your Own Cloud, and BYOC requires the Managed Deep Agents CLI and SDK at v0.10 or later.
- It is built around the Deep Agents harness, so agents written another way need a custom LangSmith Deployment.
- Almost all available documentation comes from LangChain itself, with very little independent production feedback yet.
- Everything runs on hosted infrastructure, and LangSmith lists no offline capability.
Your first hour
- Sign up at smith.langchain.com with Google, GitHub, Discord or email, and pick a data region.
- Lay out the agent as a project directory containing its instructions and tool definitions.
- Run the Managed Deep Agents deploy command against that folder.
- Open LangSmith tracing and watch the agent's first live runs.
If it isn't the fit
Deep Agents SDK4 · LangChain's open Deep Agents toolkit that you deploy and operate on your own infrastructure.
Pick it when you want maximum flexibility over hosting and runtime operations and have the people to run them.
Questions
- How does this differ from the Deep Agents library I already use?
- Both use the same Deep Agents harness. The managed version adds hosted infrastructure, the Agent Server API and tracing, while the open library leaves deployment and operations to you.
- Where does my agent's data live?
- LangSmith asks you to choose a US, EU or APAC region on GCP when you create the account. LangChain keeps a regions FAQ in its docs that is worth reading before you sign up.
The call
Point it at an internal agent this week and read the traces. Make the production call once LangChain shows what managed hosting costs.
How we scored it
Three scores out of 10, weighted and added. Value is not scored, so the other weights keep their usual proportions, scaled up to add to 100%.
Capability7.0 × 46.7% = 3.27
It packages a planning, tool-calling harness with an API, tracing and built-in web search, which covers most of what a hosted agent needs on day one. What it does
Ease of use7.5 × 26.7% = 2.00
The path is a project directory plus one deploy command, and the main friction is a region choice at signup that you cannot revisit. Your first hour
ValueNot scored, carries no weight
Not scored: the pages this review read showed no paid price, so the Koda Score is weighted over capability, ease and momentum. What it costs
Momentum5.0 × 26.7% = 1.33
On 2026-11-09 the langchain-ai/managed-deepagents repo showed 25 stars and 0 releases in the last 90 days, a quiet record for a launch with LangChain's reach.6
Read by Koda: langchain-ai/managed-deepagents on GitHub, read 2026-11-09: 25 stars; 0 releases in the last 90 days. github.com
Koda score6.6
The parts add to 6.60, rounded half up to one decimal.
Sources
- 1Managed Deep Agents · smith.langchain.com, read 9 November 2026: prices, capabilitiesReported
- 2Reddit r/LangChain · reddit.com, read 9 November 2026: the reviewer paraphrased under What people sayReported
- 3linkedin.com · read 9 November 2026: the reviewer paraphrased under What people sayReported
- 4Deep Agents SDK · docs.langchain.com, read 9 November 2026: what it isReported
- 5Langfuse · langfuse.com, read 9 November 2026: what it isReported
- 6github.com · read 9 November 2026: momentum evidenceReported
Also read, not quoted: youtube.com.
How this review was made
We read 4 pages of smith.langchain.com, ran 3 searches and read 10 community posts. Prices and product claims are reported as their source published them. The four scores are the Koda Lab's judgement; per-user prices and the total are our math.
How we scoreCorrectionsLAB REPORT 275