Managed Deep Agents explained in 2 minutes
Read the Portuguese translation →
Author: LangChain · Watch on YouTube
Video authored by the channel shown, not by IANIA; all rights belong to the creator. Transcript and summary generated automatically; the original-language content is preserved.
Original language: English
Original video: Managed Deep Agents explained in 2 minutes · Channel: LangChain · 02:10 · Watch on YouTube
Topics: AI agents
Summary
Section titled “Summary”Managed Deep Agents aims to make production deployment easier by handling infrastructure challenges that arise when scaling agents. Developers define business logic using prompts, tools, and skills, while the open-source Deep Agents harness provides the model loop, file system, and sub-agent delegation. Managed Deep Agents adds production features such as durable execution, memory, sandboxes, authentication, and deployment options including Slack bots and web apps. LangSmith Engine monitors production traces, identifies recurring failures, and drafts fixes to create a self-improving loop.
Key points
Section titled “Key points”- Deep Agents provides abstractions for tools, skills, and memory so developers can focus on agent-specific logic.
- Scaling agents in production involves challenges such as sandboxed code execution, permissions, state management, and multi-agent coordination.
- An existing Deep Agent can be deployed with a single CLI command to LangSmith.
- An agent consists of business logic, a harness, and infrastructure.
- The open-source Deep Agents harness runs business logic against a model and supports file-system use and sub-agent delegation.
- Managed Deep Agents provides production infrastructure, including durable execution, streaming, sandboxes, schedules, MCP connectors, and authentication.
- Context Hub stores instructions, skills, and memory.
- Agents can be shipped as Slack bots or web apps.
- LangSmith Engine monitors traces, clusters recurring failures, diagnoses root causes, and drafts code or prompt fixes.
Chapters
Section titled “Chapters”| Start | Chapter | Summary |
|---|---|---|
| 00:00 | Why managed agents | The video introduces Deep Agents and explains why deploying agents at production scale remains challenging. |
| 00:32 | The three layers of an agent | The video distinguishes business logic, the Deep Agents harness, and the infrastructure needed to serve users. |
| 01:05 | Production infrastructure | Managed Deep Agents supplies deployment capabilities and integrations, while LangSmith Engine supports monitoring and improvement. |
| 01:37 | Deploy and improve | The video describes a self-learning loop and summarizes how to define and deploy an agent with less repeated setup. |
Quotes
Section titled “Quotes”With managed Deep Agents, you can deploy an existing Deep Agent with a single CLI command. — 00:00
So, every agent breaks into three layers. — 00:32
Managed Deep Agents handles all of the challenges associated with deploying agents to production. — 01:05
Define your agent as a few files, run one deploy command, and it’s live. — 01:37
Concepts and entities
Section titled “Concepts and entities”Managed Deep Agents, Deep Agents, LangSmith, Context Hub, LangSmith Engine, LangChain
Full transcript (original language)
Section titled “Full transcript (original language)”00:00 Modern agent harnesses like Deep Agents have made it easier to build agents by providing the core abstractions for things like tools, skills, and memory, so you can focus on logic that’s specific to your agent. Now, although agent harnesses have made building easier, scaling in production is still hard. For example, sandbox code execution, permissions and state management, multi-agent coordination, self-improving loops, and model choice across or within threads. With managed Deep Agents, you can deploy an existing Deep Agent with a single CLI command. You just push an agent onto
00:32 LangSmith, which also bundles in a scalable runtime with tracing and evals, and you can ship and improve your agent from one place. Essentially, your agent is production ready once you deploy here. So, every agent breaks into three layers. First is the business logic, shown here in green. These are your prompts, tools, and skills, the part that only you can write. Then comes the harness, shown here in blue. This is the loop that runs your business logic against a model, plus the file system and sub-agent delegation that make the loop work. That’s our open-source Deep Agents. And finally, here’s the infrastructure,
01:05 which is everything needed to actually serve this to real users. Managed Deep Agents handles all of the challenges associated with deploying agents to production. Durable execution and streaming come from LangSmith deployments. Instructions, skills, and memory live in Context Hub. Sandboxes, schedules, MCP connectors, and auth are wired in by default, and you can ship it as a Slack bot as easily as a web app. Once you ship your agent, you need a way to And this is where LangSmith Engine steps in, our automated agent that monitors production traces, clusters recurring
01:37 failures into prioritized issues, diagnoses root causes, and drafts code or prompt fixes. With one more click of a button, you have a self-learning loop for your deployed agent. We’ve baked best practices into MDA that handle all the boilerplate we see people stand up for every agent, so you can stop rebuilding the same production stack every time. Define your agent as a few files, run one deploy command, and it’s live. If you’re interested in learning more about building and deploying agents, check out our resources.
02:10 >> [music]