Managed Deep Agents is in public beta and available on LangSmith Cloud in the US region only.
Project structure
Every capability lives in a file whose location determines its role:Compose the agent
The agent entry is the wiring diagram for the project. It imports the authored tool and middleware, then declares the model, middleware order, and which tools pause for human review. The managed runtime owns the backend, store, checkpointer, skills, and system prompt, so none are set here.interrupt_on (Python) and interruptOn (TypeScript) pause the run before the query_db tool executes, so a human can approve the call. For decision types and how to respond to interrupts, see Human-in-the-loop. For the core configuration fields, see Agent definition.
Write the instructions
instructions.md holds the managed system prompt. It sets the agent’s role and references its tools and sandbox workspace:
instructions.md
Capabilities by file
Each project file maps to a feature guide. Follow the linked page for full examples and configuration options.Run and deploy the project
Test the project locally withmda dev, then deploy it with mda deploy. Open deployment traces in LangSmith to inspect model calls, tool calls, errors, and latency.
mda deploy compiles the project, syncs instructions and skills to Context Hub, uploads the build, and reconciles the daily schedule once the deployment is live.
See also
- Quickstart: create and deploy a first agent.
- Tutorial: build an agent step by step.
Connect these docs to Claude, VSCode, and more via MCP for real-time answers.

