Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

Python authoring package and CLI launcher for Managed Deep Agents.

[!IMPORTANT] Active development / private beta. Managed Deep Agents is in active development and currently in private beta. The PyPI package API and managed runtime contract may change. Join the waitlist for access and updates.

managed-deepagents is the PyPI package for authoring Managed Deep Agents in Python. It includes:

  • define_deep_agent, the Python authoring contract for managed agents.
  • define_schedule, the Python contract for managed cron schedules.
  • mda, the CLI used to build and deploy your agent to LangSmith.
  • managed_deepagents.runtime, the runtime helper used by generated managed entry modules.

Install

uv tool install managed-deepagents

[!NOTE] Private beta: dev releases only. We currently publish only PEP 440 pre-release (dev) versions and no stable version yet. uv skips pre-releases by default unless they are allowed explicitly:

uv tool install --prerelease allow managed-deepagents

This package requires Python 3.9 or newer. Each platform wheel bundles the prebuilt mda binary for its OS and CPU architecture and exposes it through the mda console script. This PyPI-installed CLI scaffolds and compiles Python projects only and vendors the Python runtime bundled with this wheel.

To start a new project:

mda init my-agent
cd my-agent
uv sync

mda init can shape the project up front — --instructions "..." (or --instructions-file <path>) writes the system prompt, --scope <boundary> declares who may call the deployment and how runs are isolated, --model <spec> picks the model, and --no-sandbox / --no-evals leave parts out. Nothing prompts, so this is also the command to hand a coding agent or a CI script rather than having it write a project layout from memory.

mda init my-agent --interactive hands the build to the Deep Agent builder instead, which interviews you in your terminal.

Define an Agent

Create an agent.py that defines an agent:

from managed_deepagents import define_deep_agent

# The system prompt comes from instructions.md next to this file.
agent = define_deep_agent(
    name="research-assistant",
    model="openai:gpt-5.5",
    tools=[query_db],
)

define_deep_agent requires a static name (LangGraph assistant id and default LangSmith deployment name) and otherwise accepts the create_deep_agent keyword surface minus the managed keys: backend, store, checkpointer, memory, skills, and system_prompt. Those are provided by the managed runtime when your agent is deployed. Write the system prompt in instructions.md next to agent.py; the CLI embeds it at deploy time.

On deploy, Context Hub stores harness files (instructions.md, skills/**) plus a shared agent memory template and optional org-memory/** in the deployment Hub repo. When identity scopes memory to a user or organization, the runtime opens a dedicated Hub repo per caller (lazy-created) and mounts it at /memories/user/; shared agent memory still remounts a path in the deployment repo. Hot memory (/memories/user/AGENTS.md) is injected every turn. Optional org facts mount read-only at /memories/org/. Deploy never overwrites existing memories.

Project Shape

my-agent/
  agent.py              # named `agent` variable
  instructions.md       # managed system prompt
  pyproject.toml
  .env                  # local deploy secrets, never committed
  schedules/            # optional managed cron schedules
  tools/                # optional custom tools
  middleware/           # optional middleware
  skills/               # optional skills synced to Context Hub
  sandbox/              # LangSmith sandbox (`mda init` includes this; delete to opt out)
  connectors/mcp.py     # optional MCP server declaration

The CLI copies your project files into the managed build and generates the entry module that connects your definition to the hosted runtime.

The agent entry must live at the project root as agent.py.

Define a Schedule

Create one file per schedule under schedules/ and define a named schedule:

# schedules/daily_digest.py
from managed_deepagents import define_schedule

schedule = define_schedule(
    cron="0 8 * * 1-5",
    timezone="America/Los_Angeles",
    prompt="Write the daily digest.",
)

mda deploy reconciles schedules as LangSmith cron jobs after the deployment is live. Declarations must be statically serializable literals or top-level constants; prompt schedules become user-message input, and stateless runs clean up their temporary thread after completion.

Sandbox

mda init scaffolds sandbox/__init__.py with a LangSmith sandbox. MDA only enables the sandbox when that declaration is present — delete sandbox/ to opt out:

from managed_deepagents import sandboxes

sandbox = sandboxes.langsmith(
    scope="thread",
    idle_ttl_seconds=600,
)

If sandbox/setup.sh exists, MDA embeds it and runs it once when the sandbox is first provisioned. MDA owns sandbox naming, image/snapshot selection, reuse, and lifecycle.

MCP Connectors

Add connectors/mcp.py to attach MCP servers. The file must define a module-level connector. By default, MDA exposes every tool loaded from each declared server:

from managed_deepagents import connectors

connector = connectors.mcp(
    mcp_servers={
        "langchainDocs": {
            "transport": "http",
            "url": "https://docs.langchain.com/mcp",
            "include_tools": ["search", "fetch"],
        },
    },
)

Use include_tools or exclude_tools inside a server config to select a subset. Tool names are raw MCP tool names before the managed {server}__ prefix is applied, so "include_tools": ["search"] on server langchainDocs exposes langchainDocs__search when prefixing is enabled.

CLI

Create a new project:

mda init my-agent

Build locally:

mda build ./my-agent

Run on the local LangGraph dev server:

mda dev ./my-agent

mda dev requires uv on PATH, but it resolves the local LangGraph dev server automatically; you do not need to install a global langgraph command.

Deploy to LangSmith:

mda deploy ./my-agent

The generated build is written to <root>/.mda/build by default.

Common deploy options:

mda deploy ./my-agent --name my-agent-dev --deployment-type dev
mda deploy ./my-agent --workspace-id "$LANGCHAIN_WORKSPACE_ID"
mda deploy ./my-agent --no-wait

Read the deployed agent's server logs:

mda logs ./my-agent
mda logs ./my-agent --lines 200 --level error
mda logs ./my-agent > agent.log

In a terminal mda logs streams new output until you press Ctrl-C. When the output is piped or redirected it prints the most recent lines (1000 by default) and exits.

Tear it down again:

mda delete ./my-agent

mda delete (alias mda destroy) removes the LangSmith deployment, the tracing project created alongside it, the deployment's Context Hub repo including the per-user and per-organization memory repos beneath it, and the managed sandboxes the deployment created. It asks for confirmation first; pass --yes to skip the prompt in scripts. Agent memory and thread history are not recoverable afterwards.

Sandboxes are matched by name: the runtime names each one {deployment}--{digest}, which also lets a restarted deployment re-adopt its existing sandbox instead of stranding it. The digest covers the sandbox scope plus how it was provisioned, so editing setup.sh or switching snapshots gives the next run a fresh sandbox instead of one built from the previous recipe. Sandboxes created before this behavior existed are unnamed and are left to LangSmith's idle-stop and retention window.

Before deploying, make sure your model provider key such as OPENAI_API_KEY or ANTHROPIC_API_KEY is available in the project .env, the process environment, or LangSmith workspace secrets. For LangSmith itself, set LANGSMITH_API_KEY the same way, or run interactively and press Enter at the prompt to sign in with your browser. Use LANGCHAIN_WORKSPACE_ID or --workspace-id when your credentials require a workspace selection.

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distributions

No source distribution files available for this release.See tutorial on generating distribution archives.

Built Distributions

If you're not sure about the file name format, learn more about wheel file names.

managed_deepagents-0.5.0.dev82-py3-none-win_arm64.whl (2.0 MB view details)

Uploaded Python 3Windows ARM64

managed_deepagents-0.5.0.dev82-py3-none-win_amd64.whl (2.1 MB view details)

Uploaded Python 3Windows x86-64

managed_deepagents-0.5.0.dev82-py3-none-macosx_11_0_arm64.whl (2.0 MB view details)

Uploaded Python 3macOS 11.0+ ARM64

managed_deepagents-0.5.0.dev82-py3-none-macosx_10_12_x86_64.whl (2.1 MB view details)

Uploaded Python 3macOS 10.12+ x86-64

File details

Details for the file managed_deepagents-0.5.0.dev82-py3-none-win_arm64.whl.

File metadata

File hashes

Hashes for managed_deepagents-0.5.0.dev82-py3-none-win_arm64.whl
Algorithm Hash digest
SHA256 105fd8ea47f7d69d8e6e8284cbadb3f3ffafd81c35ce75d7f9108e9a066e0324
MD5 352acb1f8231e2e55afdae575a0416b6
BLAKE2b-256 65402340dcbc0b97fe4514eefc46727af3cfbb6ef56292a7a742f445e9855375

See more details on using hashes here.

Provenance

The following attestation bundles were made for managed_deepagents-0.5.0.dev82-py3-none-win_arm64.whl:

Publisher: release.yml on langchain-ai/managed-deepagents-sdk

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file managed_deepagents-0.5.0.dev82-py3-none-win_amd64.whl.

File metadata

File hashes

Hashes for managed_deepagents-0.5.0.dev82-py3-none-win_amd64.whl
Algorithm Hash digest
SHA256 497d2a14a688be5c27bcc5e9c3fccffefb069918e3caec55ec8a23c1d3de885e
MD5 af9e1ab805b12a8279d04ad16a912e6d
BLAKE2b-256 f18394aed23b7fbcf144cac1937a29370b3605759f6e6adeb556a30148ec34ea

See more details on using hashes here.

Provenance

The following attestation bundles were made for managed_deepagents-0.5.0.dev82-py3-none-win_amd64.whl:

Publisher: release.yml on langchain-ai/managed-deepagents-sdk

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file managed_deepagents-0.5.0.dev82-py3-none-manylinux2014_x86_64.whl.

File metadata

File hashes

Hashes for managed_deepagents-0.5.0.dev82-py3-none-manylinux2014_x86_64.whl
Algorithm Hash digest
SHA256 ebf090a49866923305217fe0c4e820bdd6d0618196b8f3eb4679f627df3a9a3f
MD5 1fd74ac3b920d171006410d5acc0a1e7
BLAKE2b-256 68abffc12e7d5716e6d80294fb93e03487d2d86c0bcac70f29bff542259dc24e

See more details on using hashes here.

Provenance

The following attestation bundles were made for managed_deepagents-0.5.0.dev82-py3-none-manylinux2014_x86_64.whl:

Publisher: release.yml on langchain-ai/managed-deepagents-sdk

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file managed_deepagents-0.5.0.dev82-py3-none-manylinux2014_aarch64.whl.

File metadata

File hashes

Hashes for managed_deepagents-0.5.0.dev82-py3-none-manylinux2014_aarch64.whl
Algorithm Hash digest
SHA256 498a3695e1eee297b08b6f90f4d3647b0b318794730750a96cd9bce5dd8322fc
MD5 984406c9074074e85c4db82a704406a5
BLAKE2b-256 8606b60b6237cc9be9e58408c9b54ef8cbee441739fad002bd8e6909db11be1b

See more details on using hashes here.

Provenance

The following attestation bundles were made for managed_deepagents-0.5.0.dev82-py3-none-manylinux2014_aarch64.whl:

Publisher: release.yml on langchain-ai/managed-deepagents-sdk

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file managed_deepagents-0.5.0.dev82-py3-none-macosx_11_0_arm64.whl.

File metadata

File hashes

Hashes for managed_deepagents-0.5.0.dev82-py3-none-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 a2363cf9ac384cec8119b7ee2923052d71e8b7421ff66fad48e243220b16ae32
MD5 c0289a24b654fa49a23007329106731d
BLAKE2b-256 9b4f5f5adeca75667b47842ce355b4befcbba0a4fe4963209e3ed5f3196ea792

See more details on using hashes here.

Provenance

The following attestation bundles were made for managed_deepagents-0.5.0.dev82-py3-none-macosx_11_0_arm64.whl:

Publisher: release.yml on langchain-ai/managed-deepagents-sdk

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file managed_deepagents-0.5.0.dev82-py3-none-macosx_10_12_x86_64.whl.

File metadata

File hashes

Hashes for managed_deepagents-0.5.0.dev82-py3-none-macosx_10_12_x86_64.whl
Algorithm Hash digest
SHA256 0ee447a5563911b998de4d260777e34a75b1f503923772386fedd3c437f026ef
MD5 407dbfcf2dcfe0fa91bcfdba41c50551
BLAKE2b-256 434142f0bb9cb407b87f25575ee2db0c42510383580c2ddd7a0a4b9943425afa

See more details on using hashes here.

Provenance

The following attestation bundles were made for managed_deepagents-0.5.0.dev82-py3-none-macosx_10_12_x86_64.whl:

Publisher: release.yml on langchain-ai/managed-deepagents-sdk

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Release history Release notifications | RSS feed

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page