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] Public beta. Managed Deep Agents is in public beta. The PyPI package API and managed runtime contract may change. See the docs for getting started 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, run mda init and follow the guided setup:

mda init

After scaffolding, choose a coding agent to continue building or choose View raw prompt to copy the setup instructions. The CLI supports Deep Agents Code, Claude Code, Codex, Cursor, Droid, Gemini CLI, opencode, and Pi. If Deep Agents Code is not installed, selecting it offers the official install command; on native Windows, use WSL. Coding agents open in the new project directory.

mda init can shape the project up front — --instructions "..." (or --instructions-file <path>) writes the system prompt, --model <spec> picks the model, --memory agent opts into deployment-shared durable memory, and --no-sandbox leaves out the sandbox. Every new project includes an identity.py that explicitly selects auth.langsmith_api_key() authentication. Managed Deep Agent evals are Harbor tasks under evals/tasks/. Optionally create a minimal source task under evals/scaffold/ with mda evals init <name>, then package the managed agent and scaffolded tasks with mda evals compile.

mda init my-agent --gateway runs the agent on LangSmith Gateway — a model LangSmith hosts, billed to your workspace's Gateway Credits, authenticated with a LangSmith API key instead of a model provider key of your own. It is mutually exclusive with --model, which names a provider you hold the key for.

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.

To authenticate SDK and API requests with a LangSmith workspace key while retaining MDA's thread and store authorization, declare it explicitly:

identity = define_identity(auth=auth.langsmith_api_key())

Clients send the key as x-api-key. LangSmith Cloud supplies the verification endpoint and tenant configuration; do not add those platform-owned values to the project .env.

On deploy, Context Hub stores harness files (instructions.md, skills/**). A root memory.py declaring define_memory(scope="agent") additionally mounts one deployment-shared memory tree at /memories/agent/. /memories/agent/AGENTS.md is injected every turn; other files are read on demand. Deploy never overwrites existing memories. Memory is independent of identity, and a project without memory.py mounts no durable memory.

Project Shape

my-agent/
  agent.py              # named `agent` variable
  identity.py           # managed authentication (included by `mda init`)
  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 define_sandbox

sandbox = define_sandbox(
    idle_ttl_seconds=600,
)

If sandbox/setup.sh exists, mda deploy / mda dev bake it into a recipe snapshot once; thread sandboxes clone that snapshot and do not re-run setup. MDA owns sandbox naming, image/snapshot selection, reuse, and lifecycle.

Private published images can declare registry credentials by environment variable name; MDA creates or updates the deployment-owned Host registry:

sandbox = define_sandbox(
    docker_image="ghcr.io/acme/agent-base:1",
    registry={
        "url": "ghcr.io",
        "username": "octocat",
        "password_env": "GHCR_TOKEN",
    },
)

Put GHCR_TOKEN in the project .env or process environment. Its value is used only to reconcile the registry and never enters the build or snapshot.

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. Supply your own auth via static headers when the server requires credentials:

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 (plus any legacy per-user or org child memory repos left from older runtimes), 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} of the thread id, which also lets a restarted deployment re-adopt its existing sandbox instead of stranding it. Recipe changes (setup.sh or bake base) produce a new deploy-time snapshot; live threads keep their boxes until reclaim. 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 or LangSmith workspace secrets; a value exported in your shell is not deployed. For LangSmith itself, set LANGSMITH_API_KEY in .env or your shell, 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.3.dev115-py3-none-win_arm64.whl (1.8 MB view details)

Uploaded Python 3Windows ARM64

managed_deepagents-0.5.3.dev115-py3-none-win_amd64.whl (1.9 MB view details)

Uploaded Python 3Windows x86-64

managed_deepagents-0.5.3.dev115-py3-none-macosx_11_0_arm64.whl (1.9 MB view details)

Uploaded Python 3macOS 11.0+ ARM64

managed_deepagents-0.5.3.dev115-py3-none-macosx_10_12_x86_64.whl (2.0 MB view details)

Uploaded Python 3macOS 10.12+ x86-64

File details

Details for the file managed_deepagents-0.5.3.dev115-py3-none-win_arm64.whl.

File metadata

File hashes

Hashes for managed_deepagents-0.5.3.dev115-py3-none-win_arm64.whl
Algorithm Hash digest
SHA256 fbe38eb263f350ae160b5fb80cf032599ccfacec3b173a0297754a5746149e87
MD5 f8eeec3eea895d1ec342349e94249744
BLAKE2b-256 a487f3da728ee32edc1f16665654366c22b3313aade2f650e3432e64ddc81f0a

See more details on using hashes here.

Provenance

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

File metadata

File hashes

Hashes for managed_deepagents-0.5.3.dev115-py3-none-win_amd64.whl
Algorithm Hash digest
SHA256 cb5e4a74889cde93746626115998564e74fab485bfe343adf54e69fd400db35d
MD5 ad88dd01deffbfd947f522f2c1bc9681
BLAKE2b-256 484e05d562ffe11fbbc8126a6c027c91db3e0dd1788b93b7499758ffa415c110

See more details on using hashes here.

Provenance

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

File metadata

File hashes

Hashes for managed_deepagents-0.5.3.dev115-py3-none-manylinux2014_x86_64.whl
Algorithm Hash digest
SHA256 4a4c9ca1ae54a671d39e334b5c54ba524fcc41332a61d92dbdfa443898ac73e1
MD5 e091c41800662923c6e209724c0aa791
BLAKE2b-256 4ecd62e63385d851da853eeb15d496a5f8efc42f76857a32ce3414968e5e9af3

See more details on using hashes here.

Provenance

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

File metadata

File hashes

Hashes for managed_deepagents-0.5.3.dev115-py3-none-manylinux2014_aarch64.whl
Algorithm Hash digest
SHA256 729916f8985bc5bdc81cf5c0520857f51872374cd29432ca34e61948f49f56da
MD5 890e34f0bd35a83c8035fe95635a87d8
BLAKE2b-256 2bda07a4043cf4c90c7cecf25044ca55505695fc48d1c6bb16dbd26087e49430

See more details on using hashes here.

Provenance

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

File metadata

File hashes

Hashes for managed_deepagents-0.5.3.dev115-py3-none-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 1f9110823d29d86540c53c50ce543428c7f6ce9ed9c4a64f6120753eefd1b205
MD5 d1251b42b055b56258b79824338ee5c4
BLAKE2b-256 3f6badac706eb9784db4fb2525089a6e8647a81949943b0309cc18bb4b300c29

See more details on using hashes here.

Provenance

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

File metadata

File hashes

Hashes for managed_deepagents-0.5.3.dev115-py3-none-macosx_10_12_x86_64.whl
Algorithm Hash digest
SHA256 19b00470e067a3642fe31d1bed445ebe74c006a2bc13e24eab42f88aa7609fe9
MD5 7cc858e98e020a2e89234c46f52a5c74
BLAKE2b-256 367da178bdf8a6c0730df03b7a3091318bace1788a97926c769f942362a2cba9

See more details on using hashes here.

Provenance

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

0.7.2

6 files

0.7.1

6 files

0.7.0

6 files

0.6.1

6 files

0.6.0

6 files

0.5.3

6 files

This release

0.5.3.dev115 This release

6 files

0.5.2

6 files

0.5.1

6 files

0.5.0

6 files

0.4.3

6 files

0.4.2

6 files

0.4.1

6 files

0.4.0

6 files

0.3.1

6 files

0.3.0

6 files

0.2.0

6 files

0.1.2

2 files

0.1.1

2 files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page