Claude Managed Agents

The headless deployment surface for claude-financial-services — Anthropic’s Managed Agents API (/v1/agents), the counterpart to claude-cowork in the “two ways from one source” model.

In this wiki

• Each template under managed-agent-cookbooks/ references the same system prompt and skills as its Cowork plugin counterpart, plus an agent.yaml, depth-1 leaf-worker subagents, and steering-event examples.
• A deploy script resolves file references, uploads skills, creates the subagents, and POSTs an orchestrator to /v1/agents. A reference event loop routes handoff_request events between agents via the firm’s own orchestration layer.
• Subagent delegation (callable_agents) is a Research Preview capability.
• Built on model-context-protocol connectors for data access.

Its leaf-worker subagents + handoff_request loop are an instance of agent-orchestration.

Terminal client — the ant CLI

Beyond the FSI deploy-script pattern, Anthropic now ships a first-party CLI, ant (ant-cli), that drives this /v1/agents surface directly: create → deploy to Anthropic’s cloud → send tasks → pull execution traces, “without creating any wrapper code.” It turns Managed Agents into a terminal primitive — the developer-facing edge of anthropic‘s model-provider → full-agent-platform shift.

Related

claude-financial-services · claude-cowork · ant-cli · model-context-protocol · agent-orchestration · anthropic

Sourced from the financial-services README + the ant-cli hands-on (the CLI client).

Re-verified 2026-08-04 (staleness queue)

url: added (platform docs). Status: public beta, behind the managed-agents-2026-04-01 beta header, with memory-store endpoints on a separate agent-memory-2026-07-22 header.

Two design facts worth carrying into this spoke’s agent-memory and agent-scope-isolation threads. An agent is a persisted, versioned config — model, system prompt, tools, MCP servers and skills are top-level fields on POST /v1/agents, never on a session — and every update creates a new immutable version, with sessions pinning to a version at creation. And there is no delete, only archive, which is permanent: the agent becomes read-only, no new sessions can reference it, and there is no unarchive. That is a stronger immutability guarantee than any other agent runtime in this corpus offers, and it is the opposite instinct to the mutable-markdown memory pole.