Jonathon's AI Wiki

Claude Managed Agents

10 min read

Source: Anthropic official announcement — Apr 8 2026 + earlier ai-research (web research, 2026-04-11) + raw/How_AI_Now_Does_My_Stock_Research_-_Claude_s_New_Finance_Agents_Full_Install.md (Ralph community walkthrough, 2026-05-22) Type: Product Launch Product: Claude Managed Agents Date: 2026-04-08

Blog claims now cited directly from Anthropic: +10 percentage points on structured file generation vs. standard prompting loops (internal testing); customer examples include Notion (parallel workspace tasks), Rakuten (cross-department enterprise agents), Asana (AI Teammates), Sentry (bug detection + patch writing), plus Vibecode, Atlassian, legal tech, and meeting prep applications.

Anthropic’s hosted agent service, launched April 8, 2026 in beta. Managed Agents eliminates 3-6 months of infrastructure work by providing sandboxed code execution, checkpointing, credential management, scoped permissions, and end-to-end tracing out of the box. You define agents in natural language or YAML; Anthropic handles the runtime.

What it does

  • Runs long-horizon agents on Anthropic’s infrastructure — no need to build your own sandbox, checkpointing, or credential store
  • Build and manage agents via the Console, Claude Code, or the new CLI
  • Agent definitions can be natural language or YAML
  • Built-in OAuth support: token exchange, refresh, and consent flows are handled automatically
  • All endpoints require the managed-agents-2026-04-01 beta header

Pricing

  • Runtime: $0.08 per runtime hour
  • Tokens: Standard Claude model usage pricing on top
  • Estimate: ~$58/month for a 24/7 always-on agent (before token costs)

Advanced features (limited preview)

These are not generally available yet — access is gated:

  • Memory tooling — agents persist context across runs
  • Multi-agent orchestration — coordinate multiple managed agents
  • Self-evaluation — agents assess their own output quality

Scheduled deployments + vault credentials (2026-06-09)

The W25 release wave made Managed Agents deployable on a schedule, across the SDK, cookbook, and the claude-api skill:

  • Deployments API + scheduled runs. The Python/TS SDKs (v0.109.0 / sdk-v0.104.0) added Managed Agents deployments support; the claude-api skill documents scheduled deployments — cron schedules, deployment runs, and pause / auto-pause. An agent can be provisioned once and run unattended on a schedule. See SDK releases.
  • Vault environment-variable credentials. Secrets are substituted at egress with networking allowlists, so a deployed agent gets its credentials without them living in the prompt or the codebase.
  • Worked example — Sentry-triage scheduled agent (cookbook): provisions a Managed Agent with a sentry-cli vault credential, schedules it via the deployments API, and writes a triage report each run (requires anthropic>=0.109.0).
  • Worked example — async multi-agent orchestration (cookbook): two Messages-API patterns — a fixed N-agent team with peer messaging through a shared hub, and a lead agent that spawns / monitors / dismisses async subagents. See Agent Teams.

Tokyo update — secret-injection mechanism + dreaming (2026-06-09)

[Code with Claude Tokyo 2026 — Jess Yen & Michael Cohen, MTS Managed Agents] The Tokyo managed-agents breakout (see the event digest) largely re-ran the London “production” talk — same agent / environment / session model and the user / agent / session / span event taxonomy already captured in How to get to production faster with Managed Agents. Two mechanism details beyond that coverage:

  • Vault secret-injection mechanism (concrete). An opaque placeholder token sits in the container; the real secret is injected only at network-request time, so Claude never sees the actual key — the mechanism behind the “substituted at egress” line above.
  • Dreaming. Built on memory: between runs the agent reflects on its past trajectories and codifies the lessons into curated memories. Rakuten (Yusuke Kaji, fireside) reported memory + dreaming addressed ~90% of its agents’ initial mistakes and cut latency/cost. ^[inferred — customer metric stated in-talk, auto-caption-sourced, not independently verified]

Key Takeaways

  • Managed Agents is the hosted, turnkey option for running Claude agents — you skip the infrastructure entirely
  • Natural language or YAML definitions mean non-engineers can define agent behavior
  • OAuth is built in, which removes one of the hardest parts of agent-to-service integrations
  • At 58-100+/month depending on token volume — compare with self-hosted agents on Railway/Fly/similar platforms at ~$5/month
  • Advanced features (memory, multi-agent, self-eval) are in limited preview — expect these to expand
  • Requires the managed-agents-2026-04-01 beta header on all API calls

[YouTube field-test signal — Nate Herk 2026-04-27] Hands-on test of the Managed Agents Console (raw/I_Tested_Claude_s_New_Managed_Agents..._What_You_Need_To_Know.md) surfaced operator-perspective findings the docs don’t lead with: (1) No Claude subscription required — a $5 minimum top-up on an API key is the only entry barrier (lower than Claude Code’s Pro/Max subscription), explicitly positioned as the path for chat-only users who never touched Code or Cowork. (2) Five-step Console flow: agent → environment → MCP server connections → credential vault → test run — credentials live in vaults that can be shared across team members, OAuth flow auto-handled. (3) Guided Edit caveat: describing context inside the agent chat doesn’t always update the actual system prompt (version history shows two versions identical despite chat-prompted change); the explicit “Guided Edit” button is the reliable way to mutate prompts. (4) Same toolset as Claude Code under the hood — bash / read / web search / fetch — author’s framing: “essentially the Agent SDK with a nicer wrapper.” (5) Author verdict — disappointed: “If you’re already in Claude Code this isn’t much. If you’re chat-only and never used Code or Cowork, this is a huge value-add.” Operator decision rule = chat-only users → Managed Agents; existing Code users → stick with Code/Cowork unless you need cloud sandbox + team-shared credential vaults.

  • Notion-as-managed-agent-host pattern noted: teams drag Notion tasks to a different status column, the connected Claude agent picks them up and processes — turns Notion into a queue surface, no agent UI required.

[Reddit signal — r/ClaudeCode 2026-05-10] Adjacent shipment — Anthropic financial-services reference repo. github.com/anthropics/financial-services (raw/reddit-1t9p3ho.md, 315 score / 50 comments) ships 10 prebuilt workflow agents that run either via the Claude Cowork plugin or the Managed Agents API — same agent definitions, two execution surfaces. Concretizes the “Managed Agents as the substrate for vertical-domain reference repos” thesis. The 10 agents cover the major financial verticals (investment banking, equity research, private equity, asset management):

  • Pitch Agent — fully branded pitch decks from comps, precedent transactions, LBO analysis
  • Meeting Prep Agent — pre-meeting briefing packs
  • Market Researcher — sector/theme → industry overview + competitive landscape + peer comparison + idea short list
  • Earnings Reviewer — updates models from earnings calls + filings, drafts research note outlines
  • Model Builder — works directly in Excel (DCF / LBO / three-statement / comps) in real time
  • Valuation Reviewer — aggregates GP packages, runs valuation templates for LP reporting staging
  • GL Reconciler — identifies breaks, traces root causes, routes for approval
  • Month-End Closer — accruals, rollforwards, variance commentary
  • Statement Auditor — validates LP financial statements pre-distribution
  • KYC Screener — parses onboarding documents, runs rules-based checks, flags inconsistencies Sister to the cookbook coverage of multiagent + outcomes — both ship May 2026 on the same Managed Agents API surface; cookbook is generic patterns, financial-services is the first vertical-specific reference repo from Anthropic.

[Community walkthrough signal — Ralph (chartered accountant, ex-private-equity London), 2026-05-22] Third-party YouTube walkthrough (raw/How_AI_Now_Does_My_Stock_Research_-_Claude_s_New_Finance_Agents_Full_Install.md) reframes the financial-services repo as a retail-investor surface: install path is Cowork → Customize → Browse Plugins → Personal → Add marketplace from GitHub (anthropics/financial-services repo URL), then install Financial Analysis, Equity Research, Earnings Reviewer, and Market Researcher individually. Two demoed slash-commands: /morning note on Apple (earnings reviewer pulls filings + transcripts + news into a structured brief) and /screen healthcare Europe stocks (equity research returns top names with reasoning). Load-bearing clarification for retail users: the plugins do not require paid FactSet, Bloomberg, or CapIQ connectors — Claude retrieves the underlying data from official 10-K filings directly. Paid data-connector subscriptions are only needed for self-updating reports keyed off live API price feeds.

[Anthropic announcement — 2026-05-11] Claude Platform on AWS GA. Managed Agents now distributable on AWS infrastructure with AWS authentication, billing, and commitment retirement (raw/reddit-1ta7p4n.md, ClaudeOfficial 104 score). Same-day SDK support shipped via [[claude-ai/anthropic-sdk-releases-may-2026|anthropic-sdk-python v0.101.0 + anthropic-sdk-typescript aws-sdk v0.3.0]]. Operates as a separate distribution from Amazon Bedrock — Anthropic operates the AWS service directly, ships features same-day as native API. Bedrock remains available for teams needing AWS-as-data-processor (strict regional residency, AWS-only processing). See W20 release digest for full context.

[Anthropic skills doc fix — 2026-05-17] Managed-Agents API reference: model shape correction. Commit 6a5bb06 in anthropics/skills (PR #1145, author rlancemartin) corrects the documented shape of the model field on agent create: it accepts {id, speed}, not {type: "model_config", id, speed}. The corrected shape aligns with what’s documented elsewhere in managed-agents-core.md and the request-body table. If you wired a Managed Agent create request from a draft of the reference that included the type: "model_config" wrapper, drop the wrapper.

[Anthropic cookbook — 2026-05-13] CMA Sessions API as MCP server + Linear stateless webhook bridge. Two new cookbook templates ship the off-the-shelf integration shapes for driving Managed Agents from external surfaces: (1) a thin MCP server (stdio + Streamable HTTP + bearer auth) wrapping the Sessions API so Claude Desktop / claude.ai can drive hosted CMA agents via tool calls — DIY bridge until “publish agent to claude.ai” is first-class; authoring/destructive/secret endpoints deliberately excluded so the MCP surface is read + drive only. (2) A minimal TS/Bun bridge connecting Linear’s Agent Platform to Managed Agents via CMA outbound webhooks — fully stateless (no held SSE streams, no session-map DB; session.metadata carries linear_session_id + org_id). Both proven e2e by author rlancemartin. Combined with TS sdk-v0.96.0 BetaManagedAgentsSearchResultBlock types shipped the same week, the Managed Agents production surface is now hard-wired into both the MCP ecosystem and webhook-driven third-party agent platforms. Pattern likely repeats with similar bridge templates for Slack, GitHub, Notion agents in coming weeks. See W21 Release Digest for full release-storm context and the cookbook article for implementation detail.

Try It

  1. Open the Anthropic Console and look for Managed Agents in the beta section
  2. Define a simple agent in natural language (e.g., “Monitor this GitHub repo and summarize new issues daily”)
  3. Set up OAuth credentials for any services the agent needs to access
  4. Deploy and monitor via the Console dashboard or CLI
  5. Compare the cost against self-hosted alternatives — the break-even is roughly when infrastructure maintenance exceeds $58/month
  6. AWS path: if your org has AWS commitments, install Python SDK 0.101.0 (or TS aws-sdk@0.3.0), authenticate via AWS, and target Claude Platform on AWS as the runtime — same Managed Agents surface, AWS billing.
  7. MCP bridge path (W21): install the CMA Sessions API MCP server from the cookbook to drive hosted Managed Agents from Claude Desktop or claude.ai via tool calls. Useful for teams that want operators to interact with hosted agents conversationally rather than via the Console.
  8. Linear-style webhook bridge (W21): if you run a third-party agent platform (Linear, Slack, GitHub, Notion), adapt the cookbook’s Linear template to your platform’s webhook surface. Pattern is stateless (session.metadata carries platform-specific IDs) so no session-map DB required.

Open Questions

  • What are the compute limits per agent (CPU, memory, network)?
  • How does checkpointing work — can you resume a failed agent mid-task?
  • What’s the SLA for uptime on managed agent infrastructure?
  • When will memory tooling and multi-agent orchestration move to general availability?

Graph View

Backlinks