- The Deep Agents harness: The agent loop that plans, calls tools, manages a filesystem, and delegates to subagents. See Deep Agents.
- A managed runtime: Every deployment runs on LangSmith Agent Server. You get the Agent Server API, threads, runs, streaming, and the MCP endpoint without operating the server yourself.
Example agent
A managed deep agent consists of a project folder that contains the business logic for its behavior:- Model & configuration
- Instructions
- Skills
- Tools
- Middleware
- MCP Connectors
agent.py
mda CLI, it will automatically run on managed LangSmith infrastructure.
You provide the business logic, and Managed Deep Agents provides the agent harness and production infrastructure.
To get started, see the Managed Deep Agents quickstart.
Core capabilities
Each part of the agent maps to a file or directory. Add the ones your agent needs:
For the full layout, see Project structure. Instructions, skills, and optional durable memory are stored in Context Hub.
Relationship to Deep Agents
Managed Deep Agents runs the open source Deep Agents harness rather than a second framework. The agent loop, filesystem tools, subagents, and skills are the same, so there is no second API to learn and an agent you already built keeps working. Managed Deep Agents adds the layer around the agent. The sandbox, durable memory, channels, and schedules above are declarations in a project file rather than services you build and operate. Connections run OAuth, so end users authorize their own accounts instead of you provisioning credentials for each one. LangSmith hosts the result on Agent Server. In the code, the difference is narrower: who compiles the agent.- create_deep_agent returns a compiled agent. You run it, and you own the backend, store, checkpointer, and server around it.
define_deep_agentreturns a definition. ThemdaCLI hands it to the managed runtime, which supplies those pieces along with memory, skills, and the system prompt, then compiles the agent with create_deep_agent.
define_deep_agent takes the same parameters minus the managed ones, plus a required static name. Every define_* function works this way: declare what the agent needs, and leave the lifecycle to the runtime.
Stay on Deep Agents when you run the agent yourself or need a backend, store, or checkpointer of your own. For a side-by-side comparison of the two, and the steps to convert an agent you already built, see Move from Deep Agents.
Next steps
Quickstart
Create and deploy your first Managed Deep Agent with the
mda CLI.Tutorial
Add a custom search tool, durable memory, and a daily schedule.
Agent Server
Explore the runtime that hosts Managed Deep Agents deployments.
MCP endpoint
Call a deployed agent as a tool from Claude Code or another MCP client.
Connect these docs to your agent of choice via MCP for real-time answers.

