API compatibility
Mango is an independent, self-hosted runtime that follows the documented Claude Managed Agents HTTP contract. Compatibility describes observable API and runtime behavior; Mango does not reproduce Anthropic's private scheduler, storage, sandbox, or control plane.
The Claude Managed Agents documentation and the pinned official Go SDK define the upstream target contract. This page is Mango's sole public delta ledger against that contract. Focused engineering work belongs in GitHub Issues, and shipped behavior belongs in GitHub Releases; Mango does not maintain a separate product roadmap.
Use this page to decide whether a workflow is ready for your deployment:
- Supported — implemented and exercised end to end for the stated scope.
- Limited — usable with constraints that may affect architecture or operations.
- Preview — implemented, but live-provider or production evidence is not yet strong enough for a compatibility commitment.
- Not supported — rejected explicitly rather than silently accepted.
Mango exposes 90 operations from the Managed Agents, Files, Skills, Memory, Vault, Deployment, Environment Work, and Session Thread surfaces represented by the pinned official Go SDK v1.63.1. The SDK's five separate Dreams research-preview operations are not currently exposed. Operation count is not a parity claim: accepted fields, durable behavior, provider capabilities, and deployment constraints still matter. Compatibility claims are enforced by the repository's HTTP, SDK, PostgreSQL, Temporal, and service test suites.
Capability summary
| Capability | Status | Supported scope and important constraints |
|---|---|---|
| Agents and Versions | Supported | Create, get, list, update, immutable Version history, archive, filters, and pagination. Model ID, effort, speed, and inference_geo reach working and grader requests. |
| Environments | Supported | Cloud and self-hosted lifecycle, package configuration, limited-network declarations, filters, and pagination. Package execution requires a capable sandbox; limited egress is currently enforced only by OpenSandbox. |
| Sessions | Supported | Create from immutable Agent snapshots, get/list/update/archive/delete, metadata, filters, exact shared public-list-cost budgets, usage, timing, and resource projections. Deletion fences admission and durably releases the Workflow and sandbox. |
| Events and client actions | Limited | System context, messages, thinking, tool events, confirmation/custom/self-hosted result barriers, outcomes, retries, interrupts, and the budget-boundary session.usage/budget_reached idle sequence are implemented. File-backed message documents are limited to bounded UTF-8 text; File-sourced images and File documents in tool results are not supported. |
| Event streaming | Supported | PostgreSQL-authoritative Session and Thread streams with NATS wakeups, cursor repair, bounded backpressure, and opt-in ephemeral text previews. Streams do not replay history or interpret Last-Event-ID. |
| Webhooks | Not supported | Managed Agents lifecycle webhook delivery and endpoint management remain external to Mango. The pinned SDK can verify received Standard Webhooks payloads, but Mango does not emit the documented Session, Thread, Agent, Environment, Memory, Vault, or Deployment notifications. |
| Model and context runtime | Limited | Durable provider-native transcripts, Catwalk-derived model-window profiles with a conservative fallback, provider-usage anchors plus post-anchor estimates, predictive request admission, extractive and oversized-tool-result compaction, one-shot working-turn overflow recovery, and immutable per-Thread turn-preparation checkpoints are implemented. Explicit custom-endpoint overrides, provider-exact counters, complete per-provider-request audit records, later-round projection checkpoints, equivalent Outcome/Advisor overflow recovery, and compaction quality and retention evidence remain open. |
| Sandbox tools | Limited | bash, read, write, edit, glob, and grep, plus provider-native Web Search/Fetch. Local is development-only; Docker is the current mount-capable isolated backend. |
| MCP tools | Limited | Streamable HTTP discovery/execution, permissions, journaled calls, large-result materialization, and Vault bearer/OAuth authentication. Private-network connectivity, deprecated SSE, MCP resources, and prompts are not supported. |
| Files | Limited | Five operations with configured S3-compatible storage, crash-recoverable intents, reusable snapshotted UTF-8 outcome rubrics, bounded UTF-8 File documents snapshotted into user.message, downloadable Session Resource copies, and Docker publication of regular files beneath /mnt/session/outputs before idle. Client uploads are intentionally not downloadable. File-sourced images/PDFs, non-Docker output publication, and distributed reconciliation remain open. |
| Session Resources | Limited | Five operations, independent File copies, and create-time Memory attachments. Runtime File attach/detach works. Mount execution currently requires Docker; GitHub repository resources are not supported. |
| Skills | Limited | Nine custom resource operations, immutable Version pins, strict bundle validation, Docker materialization, and on-demand Claude Code-style instruction injection. Anthropic-managed, GitHub, self-hosted, and remote-sandbox activation remain open. |
| Memory | Limited | Fourteen Store/Memory/Version operations, immutable history, SHA-256 preconditions, Docker read/write mounts, and deletion-time writeback. Non-Docker mounts and automatic retention are not implemented. |
| Dreams | Not supported | The pinned SDK exposes five dreaming-2026-04-21 research-preview operations, including the v1.63.1 output_behavior union. Mango does not yet run the asynchronous transcript-to-Memory consolidation pipeline or expose Dream resources. |
| Vaults | Limited | Thirteen Vault/Credential operations, encrypted storage, ordered Session attachment, OAuth validation, expiry refresh, and token rotation. Environment-variable egress and refresh-failure webhooks are not implemented. |
| Deployments | Limited | Ten Deployment/Run operations, pinned Agent Versions, Session budget templates, manual runs, cron scheduling, leases, and atomic success/failure records. GitHub resources and Agent-archive propagation remain open. |
| Environment Work | Limited | All eight self-hosted worker-protocol operations and official Go WorkPoller interoperability. Environment-key issuance, tenant-scoped authorization, Work secrets, and health-check Work remain open. |
| Multi-agent | Limited | Persistent ordinary child Agents plus primary-only Mango-managed Advisor consultations over standard client tool calls, independent transcripts/events/usage, shared Session list-cost budgets, reports, routing, interrupts, retries, archive, deletion, and durable context-compaction checkpoints. Exact report-only preview behavior and live Advisor lifecycle timing/targeted interruption remain open. |
| Sandbox adapters | Limited / Preview | Local and Docker are available. E2B, CubeSandbox, OpenSandbox, and Daytona have durable bindings but remain Preview pending repeated live conformance and production routing policy. |
| Distributed operation | Limited | API and worker roles scale independently around PostgreSQL, Temporal, and NATS. Worker Versioning, heterogeneous-provider routing, distributed Files reconciliation, and production rollout evidence remain open. |
Downgrading to a pre-Advisor schema requires an ordered maintenance window: drain or cancel active Sessions, run migration 33 Down with the current release, and only then deploy the older binary. The Down migration removes Advisor roster entries, private continuations, detailed Threads, and Advisor tool-journal rows while retaining the Session's already-billed aggregate usage and budget state.
Explicitly outside the current claim
Mango does not currently claim:
- hosted-infrastructure equivalence or undocumented error wording;
- end-user identity, roles, per-resource authorization, or enterprise key lifecycle (the OSS server provides Workspace-scoped API keys and tenant data isolation);
- quota, billing, audit, backup, or observability completeness;
- a supported Kubernetes or production Compose distribution;
- safe hostile multi-tenant execution on the local or Docker sandbox;
- every field or method added by a future upstream SDK release.
Unsupported behavior should fail with an explicit validation or capability error whenever it can be detected at admission time.
Verification boundary
Compatibility changes use raw HTTP/OpenAPI tests, the official Go SDK as a black-box client, PostgreSQL transaction tests, Temporal replay and integration tests, and real PostgreSQL/Temporal/NATS/MinIO/Docker service tests.
Mango has not published a versioned release. Published versions will appear in GitHub Releases. Follow the Claude Managed Agents documentation for the upstream contract, this page for Mango's current delta, and GitHub Issues for active work.