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, --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 .. Nothing prompts, so these commands also work in coding agents and CI scripts.

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)

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(
    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.

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 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.4.3.dev95-py3-none-win_arm64.whl (1.8 MB view details)

Uploaded Python 3Windows ARM64

managed_deepagents-0.4.3.dev95-py3-none-win_amd64.whl (1.9 MB view details)

Uploaded Python 3Windows x86-64

managed_deepagents-0.4.3.dev95-py3-none-macosx_11_0_arm64.whl (1.9 MB view details)

Uploaded Python 3macOS 11.0+ ARM64

managed_deepagents-0.4.3.dev95-py3-none-macosx_10_12_x86_64.whl (1.9 MB view details)

Uploaded Python 3macOS 10.12+ x86-64

File details

Details for the file managed_deepagents-0.4.3.dev95-py3-none-win_arm64.whl.

File metadata

File hashes

Hashes for managed_deepagents-0.4.3.dev95-py3-none-win_arm64.whl
Algorithm Hash digest
SHA256 e1a7a59101b4a4b011499506ba0320d52259db0a29e9a51f4deba8bae02a0ae6
MD5 4ac5366d2c63b456980a5cdaf1e4785a
BLAKE2b-256 d9645af934a592cfc8856f3a7549b854eed9c8f887578c8d40d28202a3f4fe20

See more details on using hashes here.

Provenance

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

File metadata

File hashes

Hashes for managed_deepagents-0.4.3.dev95-py3-none-win_amd64.whl
Algorithm Hash digest
SHA256 10a741211f52d69bc1ef85a1bcb97c95eb82580d6b2a57ac6d6d328c924b98d2
MD5 56d44dbf962f9f4c09c74be04f8fff8d
BLAKE2b-256 7840267ca3f142ad9af0fa981bcb34dbcd8a7b55c98c2ab6a48ccf97982787cc

See more details on using hashes here.

Provenance

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

File metadata

File hashes

Hashes for managed_deepagents-0.4.3.dev95-py3-none-manylinux2014_x86_64.whl
Algorithm Hash digest
SHA256 da2ded2912664d9030e8e008df6dbc6678a5a5c4b492c32b42a03ca14b58fb44
MD5 917f3f68ad900d8cbb0a61cab87585f5
BLAKE2b-256 b9e2d698a885d18c39823d4f4ce033213fb26d8711be7f3a875df9f1e95b7c41

See more details on using hashes here.

Provenance

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

File metadata

File hashes

Hashes for managed_deepagents-0.4.3.dev95-py3-none-manylinux2014_aarch64.whl
Algorithm Hash digest
SHA256 6d3f1749ef55fa2f01a3cd72284eba85ab2c4a9bac31ed6a03decadb2eb5f475
MD5 e921fc9b7a6362dee2ac9ce6d7bcdbb6
BLAKE2b-256 81d8855df6120e0b6e91ccb0cb6dd24d924f9e73730566f0c66173c3d03f520d

See more details on using hashes here.

Provenance

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

File metadata

File hashes

Hashes for managed_deepagents-0.4.3.dev95-py3-none-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 983953d6fa43eaed558ccbe8c8f43497c42289996432b631ba34c0bd099fe07d
MD5 e8ebc40ff91ce7216c147bfdb786d425
BLAKE2b-256 cfc8999e0f50cd8de9f199d8148607670d426dc0eb6aeb2386a63102a31477d2

See more details on using hashes here.

Provenance

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

File metadata

File hashes

Hashes for managed_deepagents-0.4.3.dev95-py3-none-macosx_10_12_x86_64.whl
Algorithm Hash digest
SHA256 89c92f708c6b8a59e3006a50d7227a972e747c80018810b6ae89ef2ff6fc7d1b
MD5 baf158e058b7e4fbc822fc1d414072a3
BLAKE2b-256 fb6756c743c0124d38f63f64c5fb22f32244873844f1ee61f1b8444a60fa3d77

See more details on using hashes here.

Provenance

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