This release is a pre-release and may not be stable for production use.
Python authoring package and CLI launcher for Managed Deep Agents.
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
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.
-
From the project root, initialize the eval workspace:
mda evals init -i
-
Follow the coding-agent prompt to author tasks directly under
evals/<task>/. The CLI creates the user-ownedevals/harbor-job.jsononce and preserves later edits..mda/evals/is generated. A task may include an authoredevals/<task>/identity.jsonfixture. It requires a non-emptyuser.id;user.kind,user.email, and top-levelgroups,claims, andsource.providerare optional. Keep it with the task, not in generated.mda/evals/. -
Export
LANGSMITH_API_KEY,LANGSMITH_WORKSPACE_IDwhen your credentials require it, and the model or tool credential variables used by the agent. -
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
MDAJobPluginandLangSmithPlugin. It uses POSIX syntax on macOS/Linux and PowerShell on native Windows. -
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 enables agent and user memory independently:
from managed_deepagents import MemoryLayer, define_memory
memory = define_memory(
agent=MemoryLayer(),
user=MemoryLayer(),
)
Omit a layer to disable it. A layer with no allow callback uses its default
policy. Agent memory is shared across callers and is available by default.
User memory requires a trusted person and defaults to managed Slack one-to-one
DMs (the original provider event has channel_type == "im"). Shared
conversations, missing event data, and direct API runs get no user mount unless
an authored policy allows it.
Either layer can use a sync or async allow(context) callback to replace its
default policy:
from typing import TypedDict
from managed_deepagents import ManagedChannelContext, MemoryLayer, define_memory
class Context(TypedDict):
remember: bool
def allow_memory(context: Context | ManagedChannelContext) -> bool:
return not isinstance(context, ManagedChannelContext) and context.get("remember") is True
memory = define_memory(
agent=MemoryLayer(),
user=MemoryLayer(allow=allow_memory),
)
Each callback runs once before memory mounts on each run, including interrupt
resumes. Returning false removes only that layer's mount and hot memory for
the run. If the context cannot satisfy the policy schema, MDA denies that layer
without calling its policy. An error from the callback still fails the run.
User policies cannot grant access to another
person's memory or grant user memory to a service principal. Build, schema, and
state inspection do not call either policy.
The legacy scope option remains supported. Do not combine it with agent or
user.
User hot memory and agent hot memory with an allow policy are loaded for each
model call. They are not saved in thread state. This keeps the graph structure
stable and prevents a later denied run from loading saved memory. A missing
hot file stays empty until the first memory write.
The agent layer is mounted at /memories/agent/. The user layer requires
identity.py and is mounted from an opaque per-user Context Hub repo at
/memories/user/, keyed on the trusted caller principal. Each mount's
AGENTS.md is injected every turn; other files are read on demand. Deploy never
overwrites existing memories. A project without memory.py mounts no durable
memory.
Run context and channels
The runtime separates application data, trusted caller information, and the current channel delivery:
runtime
.context // Application data, or MDA's managed channel context
.server_info // Trusted caller and server information
.channel // Present for a managed channel delivery
.name // Configured channel name
.provider // Provider label, such as slack
.event // Typed MDA delivery; no internal routing
.raw_event // Optional original provider payload
.post(...) // Present when sending is supported
.backend // Present when a sandbox is configured
API callers supply application data through Agent Server's context parameter:
await client.runs.create(
thread_id,
assistant_id,
input={"messages": [{"role": "user", "content": "Hello"}]},
context={"remember": True},
)
Direct API runs use your authored context_schema. Managed channel runs instead
use MDA's Pydantic context schema and receive a typed channel field, including
the current event and reply routing data. Your application's required context
fields do not apply to channel runs. Tools, middleware, and memory policies that
handle both run sources must account for both context shapes.
The factory selects the schema from the authenticated run source and passes it
to LangGraph. Context follows native LangGraph validation and parsing behavior;
MDA does not replace context during execution. Supplying a channel field in a
direct API call does not establish a trusted channel source.
ManagedChannelContext is a public Pydantic model exported by
managed_deepagents. Its channel field is a ChannelContext TypedDict validated
by Pydantic. The nested channel and event values remain JSON-compatible dictionaries.
On a channel run, use runtime.context.channel["event"] for the typed event and
runtime.context.channel.get("raw_event") for optional provider data.
MDA prepares context and memory access in the graph factory for each run or
resume. Python Agent Server supplies this through
runtime.execution_runtime.context. Direct callers of the managed compiler must
build a fresh graph with the execution's context; a compiled graph is scoped to
that execution.
runtime.channel describes the current verified delivery. It is absent on
ordinary API and schedule runs. Its facts are available even when the channel
cannot send. post uses the verified reply target from context.channel.
if runtime.channel is not None and runtime.channel.post is not None:
await runtime.channel.post({"type": "content", "content": "I am checking that now."})
The built-in Slack channel sends through Trigger and supports text content only.
It rejects native payloads and content it cannot send. For channels that support
native messages, set type to "native" and supply the JSON in native.
For content messages, set type to "content" and supply content.
Supply only the matching payload. Native JSON has no extra provider or payload
wrapper. The runtime.channel helper has no address, update, or destination override.
A post sends an additional message; the normal final agent reply remains automatic.
The event types are message, user_prompt_response, and interrupt_resume.
Message events contain messages. Prompt responses contain action, optional
value, and optional correlation_id. Resume events contain resume.
For Trigger Slack deliveries, raw_event is the inner provider event. It excludes
HTTP headers and the outer Trigger envelope. A resume can omit the raw event;
MDA does not reuse the previous delivery's event.
For a prompt that answers an interrupt, put a shared ID on the prompt and on the
interrupt value under INTERRUPT_CORRELATION_KEY. MDA uses correlation_id to
select that interrupt. Without a correlation ID, an answer can resume the only
pending interrupt; multiple pending interrupts require a match. Existing resume
values are unchanged.
The managed runtime fields are available to authored tools and middleware,
including declarative subagents, without an identity or sandbox declaration.
Channel projects still require an identity declaration for trusted ingress.
server_info preserves platform information and adds managed caller information
when available. Its link.status currently reports not_required; it does not
perform an account-link lookup. Its source thread identifier retains the existing
provider-thread/LangGraph-thread fallback behavior.
HTTP channels
Use channels.http(provider=..., verify=..., parse=..., post=...) for a
provider webhook. MDA has no built-in Slack HTTP adapter. Your application
supplies the adapter: verify checks the request signature, parse selects the
input message, and the optional async post(message) sends replies. The built-in
channels.slack() continues to use Trigger.
A message returned by parse contains user_id, thread_id, content, and
target. thread_id is the stable LangGraph thread UUID. target is separate
JSON that the adapter needs to reply, such as a Photon conversation ID or a Slack
channel and thread timestamp. MDA exposes this target at
runtime.context.channel["target"] and binds it to runtime.channel.post. The
original JSON webhook is available at runtime.context.channel.get("raw_event");
post(message) receives the target for reply routing.
HTTP runs use the same managed Pydantic context schema as Slack Trigger runs.
Memory policies receive allow(context) and can read the delivery at
context.channel. Direct API runs continue to use the authored context schema.
The callback receives one HttpChannelPostInput dictionary:
{"type": "content", "content": "The job is complete.", "target": {"conversation": "provider-thread"}}
{"type": "native", "native": {"blocks": []}, "target": {"conversation": "provider-thread"}}
It returns HttpPostedMessage, with a required id and optional url. Both types
are exported by managed_deepagents. The callback can create or reuse its provider
client directly; MDA does not call a client factory before accepting the webhook.
A callback error is a delivery failure. content is a portable message string or
content blocks. native is JSON for the provider, such as a Slack Block Kit
message. Supply exactly one form. A Slack adapter can use the provider's text field inside native as the
fallback for its blocks. That field is part of the Slack payload; it is not a
second MDA content field. The adapter validates native data and uses its bound
target and credentials when it calls the provider API. Native routing or
authentication fields must not replace them.
Automatic agent replies use the content form. An explicit
await runtime.channel.post({"type": "native", "native": ...}) reaches your
adapter without conversion. If post is omitted, the channel can receive events
and exposes facts, but has no runtime post method. The webhook path is
/channels/<name>/events, where <name> is the channel file name. An existing
Photon webhook needs no URL change when the deployment host and channel name
stay the same.
Project Shape
my-agent/
agent.py # named `agent` variable
identity.py # managed authentication (included by `mda init`)
memory.py # optional durable-memory declaration
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.
Authored tools and middleware can use the Deep Agents backend interface at
runtime.backend. It is None when the project has no sandbox:
from managed_deepagents import ManagedDeepAgentRuntime
def write_report(runtime: ManagedDeepAgentRuntime) -> None:
if runtime.backend is None:
raise RuntimeError("This tool requires a sandbox")
result = runtime.backend.write("/workspace/report.txt", "Report ready")
if result.error:
raise RuntimeError(result.error)
The backend uses the standard Deep Agents file arguments and results: ls,
read, write, edit, grep, and glob. delete is optional and depends on
the installed backend. Use upload_files and download_files for binary data.
Python also has async methods such as aread, awrite, and adelete.
All paths refer to the current sandbox. Context Hub routes for skills and
memory are not part of this backend.
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"}),
},
"exa": {
"transport": "http",
"url": "https://api.smith.langchain.com/v1/managed-tools/servers/exa/mcp",
},
},
)
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.
When a LangSmith-managed OAuth MCP server needs authorization, the runtime reports its connection URL; complete OAuth there, then retry the run. API-key MCP servers require the caller to connect the key in LangSmith Tools before invoking one of their tools.
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.
Select the deployment's Python version in pyproject.toml:
[project]
requires-python = ">=3.11"
[tool.mda]
python-version = "3.14"
Use a quoted major.minor from 3.11–3.14. MDA writes that version into the
generated langgraph.json and selects the matching Agent Server image.
requires-python remains the project's compatibility requirement.
MDA_PYTHON_VERSION overrides the project setting for one build. Without
either setting, MDA selects the newest supported version allowed by
requires-python, or 3.14 if no requirement is declared. MDA rejects
incompatible targets and warns when the image's exact patch version determines
compatibility. The dependency install checks the actual interpreter.
Set python-version explicitly to keep the same minor version when MDA adds
support for newer Python versions.
This selects the deployment image's Python version. Local build processing,
mda dev, Harbor task images, and execution sandboxes use separate interpreters.
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.
1 maintainer
Release files for managed-deepagents 0.8.0.dev6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| managed_deepagents-0.8.0.dev6-py3-none-win_arm64.whl | Python 3 | none | Windows ARM64 | Details |
| managed_deepagents-0.8.0.dev6-py3-none-win_amd64.whl | Python 3 | none | Windows x86-64 | Details |
| managed_deepagents-0.8.0.dev6-py3-none-manylinux2014_x86_64.whl | Python 3 | none | Linux glibc 2.17+ x86-64 | Details |
| managed_deepagents-0.8.0.dev6-py3-none-manylinux2014_aarch64.whl | Python 3 | none | Linux glibc 2.17+ ARM64 | Details |
| managed_deepagents-0.8.0.dev6-py3-none-macosx_11_0_arm64.whl | Python 3 | none | macOS 11.0+ ARM64 | Details |
| managed_deepagents-0.8.0.dev6-py3-none-macosx_10_12_x86_64.whl | Python 3 | none | macOS 10.12+ x86-64 | Details |
Total release size: 14.1 MB
Release files / managed_deepagents-0.8.0.dev6-py3-none-win_arm64.whl
| Download URL | managed_deepagents-0.8.0.dev6-py3-none-win_arm64.whl |
|---|---|
| Size | 2.1 MB |
| Tags | Python 3 Windows ARM64 |
|
SHA-256 checksum How to use checksums |
4a049576cf96bbf7e22deed2e215ae1bef2efb1c36974c555aefb253d67c0637
|
|
BLAKE2b-256 checksum How to use checksums |
9342c0f00fcbe5dd6c940774f73c23deeaf822cdcc662d26a36a6b65386b42af
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 18, 2026.
Transparency logRelease files / managed_deepagents-0.8.0.dev6-py3-none-win_amd64.whl
| Download URL | managed_deepagents-0.8.0.dev6-py3-none-win_amd64.whl |
|---|---|
| Size | 2.2 MB |
| Tags | Python 3 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
b79f2d8978fc5d9e616e0f0b043fe553ee977112626ab875adb069d32d76a7b2
|
|
BLAKE2b-256 checksum How to use checksums |
50c79643cc4df3b6c49a73917a6daced842cc968133e651ee9d3356cdb2e401a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 18, 2026.
Transparency logRelease files / managed_deepagents-0.8.0.dev6-py3-none-manylinux2014_x86_64.whl
| Download URL | managed_deepagents-0.8.0.dev6-py3-none-manylinux2014_x86_64.whl |
|---|---|
| Size | 2.7 MB |
| Tags | Linux glibc 2.17+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
6aad2abcd32774820624c6e5745984a89c08af9d58b6f486c19355eccf333a6a
|
|
BLAKE2b-256 checksum How to use checksums |
bda0f44d1a0b0c2d7aae4cdcaa274ea35b38162544e6b5b4d58252072ac3c5b1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 18, 2026.
Transparency logRelease files / managed_deepagents-0.8.0.dev6-py3-none-manylinux2014_aarch64.whl
| Download URL | managed_deepagents-0.8.0.dev6-py3-none-manylinux2014_aarch64.whl |
|---|---|
| Size | 2.4 MB |
| Tags | Linux glibc 2.17+ ARM64 Python 3 |
|
SHA-256 checksum How to use checksums |
0bf4dd26a64c5607a1bcf110b523d7958de3399da51c05f4735089564cd2d511
|
|
BLAKE2b-256 checksum How to use checksums |
d77cd8de6deb83e70a93dee1011780815f9bc356e07efc4eb2a25caf077dd0b0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 18, 2026.
Transparency logRelease files / managed_deepagents-0.8.0.dev6-py3-none-macosx_11_0_arm64.whl
| Download URL | managed_deepagents-0.8.0.dev6-py3-none-macosx_11_0_arm64.whl |
|---|---|
| Size | 2.2 MB |
| Tags | Python 3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
d76532b7db89461873c834a30ba79bcd78f9603d771f78de54e94107aebe0d81
|
|
BLAKE2b-256 checksum How to use checksums |
0681dfd7256ee3c804611e8080123f4f77a9d394bbf11994e724fa9644e407e4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 18, 2026.
Transparency logRelease files / managed_deepagents-0.8.0.dev6-py3-none-macosx_10_12_x86_64.whl
| Download URL | managed_deepagents-0.8.0.dev6-py3-none-macosx_10_12_x86_64.whl |
|---|---|
| Size | 2.4 MB |
| Tags | Python 3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
9106a9c1150c83c69b11fde2e857cdf7aaf43d104f13743d74836f6cf65603e7
|
|
BLAKE2b-256 checksum How to use checksums |
d0232b4fb2ca4eb01f435eecabb9aeeb9c9170d0184fcc8c3420bef780f3d0ee
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 18, 2026.
Transparency log
