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 in the deployment Hub repo. Identity memory is slice-based: the agent slice mounts at /memories/agent/ from the deployment repo, and an optional user slice opens a dedicated Hub repo per caller (lazy-created) at /memories/user/ (partitioned by user or organization). Hot memory (/memories/agent/AGENTS.md and/or /memories/user/AGENTS.md) is injected every turn for enabled slices. 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 "$LANGSMITH_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 (the CLI creates a key and writes it to .env). Use LANGSMITH_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.dev88-py3-none-win_arm64.whl (2.0 MB view details)

Uploaded Python 3Windows ARM64

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

Uploaded Python 3Windows x86-64

managed_deepagents-0.5.0.dev88-py3-none-macosx_11_0_arm64.whl (2.1 MB view details)

Uploaded Python 3macOS 11.0+ ARM64

managed_deepagents-0.5.0.dev88-py3-none-macosx_10_12_x86_64.whl (2.2 MB view details)

Uploaded Python 3macOS 10.12+ x86-64

File details

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

File metadata

File hashes

Hashes for managed_deepagents-0.5.0.dev88-py3-none-win_arm64.whl
Algorithm Hash digest
SHA256 5acb6da82d791cf26181f80d8b5defc4aaf2094afed94cf29afd5884647f0310
MD5 f57714627cb0cff067c11f518ab82be6
BLAKE2b-256 30367363a39d62a21d4b0abc5e116c87b4ca2e74acdd47e07c0ae1a88b3dcd81

See more details on using hashes here.

Provenance

The following attestation bundles were made for managed_deepagents-0.5.0.dev88-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.dev88-py3-none-win_amd64.whl.

File metadata

File hashes

Hashes for managed_deepagents-0.5.0.dev88-py3-none-win_amd64.whl
Algorithm Hash digest
SHA256 7c2dab885f0ad06102536f8264fcd5e5c4fd35b70875dc9d0db0a4c932e78325
MD5 7a03c02050ff6f74a24af7646a5602aa
BLAKE2b-256 eb4eeeb0fd8c5944b05c5ecfe99e540f8c25d7050d70cdc8e11f53f48fe1eea7

See more details on using hashes here.

Provenance

The following attestation bundles were made for managed_deepagents-0.5.0.dev88-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.dev88-py3-none-manylinux2014_x86_64.whl.

File metadata

File hashes

Hashes for managed_deepagents-0.5.0.dev88-py3-none-manylinux2014_x86_64.whl
Algorithm Hash digest
SHA256 e7953abcca7cced8d34aeabdd970adbf5ab6a597dbeda9216ec9d8b0ace77f80
MD5 aecf7ffa4e4461fda1367d41e5022cb6
BLAKE2b-256 3c85dbd3df199b6079e07dd6d1266b4350d3350f32da515ff7224cdbaa7b12f0

See more details on using hashes here.

Provenance

The following attestation bundles were made for managed_deepagents-0.5.0.dev88-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.dev88-py3-none-manylinux2014_aarch64.whl.

File metadata

File hashes

Hashes for managed_deepagents-0.5.0.dev88-py3-none-manylinux2014_aarch64.whl
Algorithm Hash digest
SHA256 8ec0a520d07253858d110bc7f5bac64687a0a9e1bf86f7fe6c02aa1bbd459479
MD5 c3807b12caa77d375d00a3086140dbe2
BLAKE2b-256 f7a394cb54d45dec7017d862290f90a81bd2be9dc55da37c7ff665b0a8450a44

See more details on using hashes here.

Provenance

The following attestation bundles were made for managed_deepagents-0.5.0.dev88-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.dev88-py3-none-macosx_11_0_arm64.whl.

File metadata

File hashes

Hashes for managed_deepagents-0.5.0.dev88-py3-none-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 e52254b99fb18a53199a641470cfb6519699e7da4290bb760140c7d9f130e166
MD5 932cf27a95093866a153aa929b41b881
BLAKE2b-256 0dd06781f1699d063d5adc65f781a522a9652b0f9ed54ce4b040b9ad8e52778f

See more details on using hashes here.

Provenance

The following attestation bundles were made for managed_deepagents-0.5.0.dev88-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.dev88-py3-none-macosx_10_12_x86_64.whl.

File metadata

File hashes

Hashes for managed_deepagents-0.5.0.dev88-py3-none-macosx_10_12_x86_64.whl
Algorithm Hash digest
SHA256 6aac971438a666f277ef80d99dae432c8a7b84361dc8d28874f0354a934f3ec9
MD5 1c815d70e4d91209ddf5cc71b5e68f6d
BLAKE2b-256 6790489fb741beb6c75aacb562d35af00e23f7ac09d7c8db3680a1254c16a36e

See more details on using hashes here.

Provenance

The following attestation bundles were made for managed_deepagents-0.5.0.dev88-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