mda dev locally. Then add a search tool, use durable memory, run the agent on a daily schedule, and deploy it to LangSmith.
For a complete project that uses every primitive, see the example project.
Managed Deep Agents is in private beta, available on LangSmith Cloud in the US region only. Join the waitlist to request access.
Build the agent
Write the instructions
Replace
instructions.md with the research assistant’s behavior. The instructions reference the tool you add next and the durable memory the runtime provides:instructions.md
Add a search tool
Create a Import the tool into the agent entry and pass it to the definition:For more on authored tools, see Custom tools.
tools/ module with a search tool, then import it into the agent entry. This example returns a placeholder result, so it runs without an external API. Replace the body with a call to your search provider.Run the agent locally
Install dependencies and start the local dev server:
mda dev opens the agent in LangSmith Studio. Send a question and confirm the agent calls web_search and answers with the returned snippets.Use durable memory
Managed memory is on by default, so you do not configure a backend. The runtime stores durable memory in Context Hub, and the agent reads and writes it during runs. Because the instructions tell the agent to remember topics of interest, tell it a preference in one turn (“I only care about open-source releases”), then start a new conversation and confirm it recalls the preference.To turn off managed memory, set
disable_memory=True or disableMemory: true in the agent definition. For how memory persists, see How Managed Deep Agents work.Schedule a daily digest
Add a
schedules/ module so the agent runs on a cron cadence without a user message. This schedule runs every weekday at 8am Pacific:mda deploy reconciles this schedule into a LangSmith cron job after the deployment is live. For thread behavior and constraints, see Schedules.Deploy the agent
Deploy the project to LangSmith:On success, the CLI prints the deployment dashboard URL. The deploy syncs the instructions to Context Hub, uploads the compiled project, and reconciles the daily schedule. For deploy flags and troubleshooting, see Deploy an agent and the CLI reference.
Next steps
Custom middleware
Add logging, retries, limits, and guardrails around model and tool calls.
Connect MCP tools
Load tools from remote MCP servers.
Example project
See a complete project that uses every primitive.
How it works
Understand compilation, the deploy lifecycle, and Context Hub.
Connect these docs to Claude, VSCode, and more via MCP for real-time answers.

