Skip to main content
This page walks through a complete Managed Deep Agents project: a customer-support agent that looks up data with a tool, redacts PII and logs an audit line with middleware, pauses for review before sensitive actions, runs a daily check-in on a schedule, loads a research skill on demand, and works in a managed sandbox. Use it as a reference for how the pieces fit together.
Managed Deep Agents is in private beta, available on LangSmith Cloud in the US region only. Join the waitlist to request access.

Project structure

Every capability lives in a file whose location determines its role:
For the packaging rules behind this layout, see How Managed Deep Agents work and the CLI project file reference.

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 backend, store, checkpointer, memory, skills, and the 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 full list of fields, see the agent definition reference.

Write the instructions

instructions.md holds the managed system prompt. It sets the agent’s role, references the tools and sandbox workspace, and states memory rules:
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 with mda 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