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. In a terminal, the CLI asks you to name the agent:

mda init

Run mda init -i to initialize your agent interactively and optionally hand it off to a coding agent to build:

mda init -i

Choose a coding agent to continue in the new project, or select View raw prompt to copy the setup instructions.

For coding agents and other headless use, pass the project name:

mda init my-agent

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, --no-sandbox leaves out the sandbox, and -c slack (also --channel / --channels) writes channels/slack.py. Every new project includes an identity.py that explicitly selects auth.langsmith_api_key() authentication.

Evaluate

Managed Deep Agent evals run in Harbor. Install uv and Docker before running them.

  1. From the project root, initialize the eval workspace:

    mda evals init -i
    
  2. Follow the coding-agent prompt to author tasks directly under evals/<task>/. The CLI creates the user-owned evals/harbor-job.json once and preserves later edits. .mda/evals/ is generated. A task may include an authored evals/<task>/identity.json fixture. It requires a non-empty user.id; user.kind, user.email, and top-level groups, claims, and source.provider are optional. Keep it with the task, not in generated .mda/evals/.

  3. Export LANGSMITH_API_KEY, LANGSMITH_WORKSPACE_ID when your credentials require it, and the model or tool credential variables used by the agent.

  4. From the same project root, run the pinned Harbor 0.21.0 command included at the end of the coding-agent prompt. The command loads MDAJobPlugin and LangSmithPlugin. It uses POSIX syntax on macOS/Linux and PowerShell on native Windows.

  5. From the same project root, inspect results:

    uv run --python 3.12 --with 'harbor[langsmith]==0.21.0' harbor view .mda/evals/jobs
    

MDAJobPlugin compiles a fresh eval artifact at every Harbor job start. This POC keeps MDA's custom Harbor adapter; migration to Harbor's built-in LangGraph agent is deferred.

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 and MCP declaration
    mcp.py              # optional MCP server declaration
  middleware/           # optional middleware
  skills/               # optional skills synced to Context Hub
  sandbox/              # LangSmith sandbox (`mda init` includes this; delete to opt out)

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 Servers

Add tools/mcp.py to attach MCP servers. The file must define a module-level mcp. By default, MDA exposes every tool loaded from each declared server. In mda dev, an agent-owned connection reads from MDA_DEV_<SLUG> with the slug uppercased and hyphens changed to underscores. Hosted deployments resolve workspace connections from Agent Auth:

The old connectors/mcp.py file API remains available with a warning during 0.7.x. It will be removed in 0.8.0.

from managed_deepagents import define_mcp, connections

mcp = define_mcp(
    servers={
        "langchainDocs": {
            "transport": "http",
            "url": "https://docs.langchain.com/mcp",
            "include_tools": ["search", "fetch"],
            "connection": connections.get("docs-token", {"type": "agent"}),
        },
    },
)

For this example, set MDA_DEV_DOCS_TOKEN.

A user-owned connection — connections.get(slug, {"type": "user"}) — resolves per caller (OAuth or opaque). Any runtime access interrupts the run when a grant is missing, including access from a custom tool or middleware. Connector declarations use the same behavior in a pre-run gate, so all known grants can be requested before the first model call. This path works in mda deploy and mda dev when LANGSMITH_API_KEY and LANGSMITH_WORKSPACE_ID are set and the workspace connection rows exist. Signed-in Studio users are identified by their LangSmith ls_user_id. Local development uses separate user connections from deployed Studio. OAuth completes on LangSmith’s platform callback URL. The local UI must show credential_authorization_required and resume after the user connects.

Deploy the project first, then provision its connections with mda connections create. Agent-owned opaque secrets are scoped to that deployment, so the command refuses to create one before mda deploy. mda deploy fails when a slug a project declares is missing from the workspace.

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.7.1.dev10-py3-none-win_arm64.whl (2.0 MB view details)

Uploaded Python 3Windows ARM64

managed_deepagents-0.7.1.dev10-py3-none-win_amd64.whl (2.1 MB view details)

Uploaded Python 3Windows x86-64

managed_deepagents-0.7.1.dev10-py3-none-macosx_11_0_arm64.whl (2.1 MB view details)

Uploaded Python 3macOS 11.0+ ARM64

managed_deepagents-0.7.1.dev10-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.7.1.dev10-py3-none-win_arm64.whl.

File metadata

File hashes

Hashes for managed_deepagents-0.7.1.dev10-py3-none-win_arm64.whl
Algorithm Hash digest
SHA256 e83195f9afb0025debf023835db6f43e5b660592df1fff6880a5b2cc9700a7b9
MD5 6ef5ead7159486ddd69e6cca21b00a53
BLAKE2b-256 2488f9459c266d1eaa916582ef19b4fabac71261b657844f757ed230a705b8da

See more details on using hashes here.

Provenance

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

File metadata

File hashes

Hashes for managed_deepagents-0.7.1.dev10-py3-none-win_amd64.whl
Algorithm Hash digest
SHA256 3ec41ee60a5ee4b95b265995fd8a44b27fa98c452ef835e062bf2a78962ac5c1
MD5 2b7f66056b120a08d1c1a1e151db0e77
BLAKE2b-256 f64793602826515decd20fe62b3523f563a84db0b83daa912af01c88282d0911

See more details on using hashes here.

Provenance

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

File metadata

File hashes

Hashes for managed_deepagents-0.7.1.dev10-py3-none-manylinux2014_x86_64.whl
Algorithm Hash digest
SHA256 ee9fa0c9a830da1d0e56f11f109bcdf2583e256e24b0e5a252798275ac818376
MD5 4a57da074af8ccfc8ee35b727fb7d4c4
BLAKE2b-256 ba939eddb6a7550efdda8d070a282ec6a8c5c32667cade7b3025e462a7e0a86d

See more details on using hashes here.

Provenance

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

File metadata

File hashes

Hashes for managed_deepagents-0.7.1.dev10-py3-none-manylinux2014_aarch64.whl
Algorithm Hash digest
SHA256 647c51556449f45a56c48866c803c9c84256b99408e873ffc68d8667ce0de457
MD5 82981a541b159a916f8db2215e266aa2
BLAKE2b-256 bd634c9d437cc2ce5145c010c25beae278b0d49c27e5b54b1d42a9ac511835d4

See more details on using hashes here.

Provenance

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

File metadata

File hashes

Hashes for managed_deepagents-0.7.1.dev10-py3-none-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 52b69b7dd1659d28709ded2d05ea1660219b41881aaa7eb08a849a88565be6d5
MD5 e1f67aa273e0faad69bc03fe37d3e018
BLAKE2b-256 b6fccdbbd27448d518ec90a52935063abcd2eae11a80f66d3b8c33758d98796e

See more details on using hashes here.

Provenance

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

File metadata

File hashes

Hashes for managed_deepagents-0.7.1.dev10-py3-none-macosx_10_12_x86_64.whl
Algorithm Hash digest
SHA256 558e6f4af1b64da4e5f8497d5909889f9c38fb46044f3dcd8f2357253736d83a
MD5 6735ff1a6a125540dd55011685ed3e43
BLAKE2b-256 34aef52e9fc97a27ed8fe0039c12007e043f64efb3ef300850ef88b4756fc069

See more details on using hashes here.

Provenance

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

This release

0.7.1.dev10 This release

6 files

0.7.0

6 files

0.6.1

6 files

0.6.0

6 files

0.5.3

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