Claude Managed Agents are Anthropic-hosted agents with bundledDocumentation Index
Fetch the complete documentation index at: https://docs.ntropii.com/llms.txt
Use this file to discover all available pages before exploring further.
bash / write / read tooling, Skills (e.g. the docx skill for Word document generation), MCP server bindings authenticated via Anthropic Vaults, and Environments for custom pip packages. Ntropii integrates with them via ntro.workflow.agents.invoke from inside a runbook step.
This page is the end-to-end walkthrough for the production adapter. The working reference implementation lives in claude-managed-agents on GitHub.
When to use
Reach for a Managed Agent when a runbook step needs LLM-driven artefact generation that doesn’t fit the deterministic capabilities surface:- Multi-section narrative documents (auditor handover .docx, NAV pack PDF, year-end letter)
- Open-ended document drafting where the structure varies by period
- Tasks where the agent benefits from
bash+python-docx+ thedocxSkill working together in a sandbox
ntro.ai.extract and ntro.ai.check. They’re cheaper, faster, and observable through the same Reasoning tab.
Lifecycle
1. Build on Anthropic Console
Author the agent in Anthropic Console. The shape of an agent.yaml that registers cleanly with Ntropii:| Object | Carries | Notes |
|---|---|---|
| Agent | name, model, system, tools, mcp_servers, skills | Per-agent definition |
| Environment | pip packages (python-docx, ntro, …), networking, metadata | Reusable across agents |
| Vault | API keys (Ntropii agent API key) | Injected into MCP server auth at session start |
2. Register with Ntropii
Once the agent exists in Anthropic Console and you have its native id (e.g.agent_01SxpziMunFrUbnAYkGB5Hu3):
external_ref, and an API key plaintext shown once.
3. Store the API key in an Anthropic Vault
Create a Vault on Anthropic, paste the plaintext API key, and reference the Vault from the agent. The Ntropii MCP server uses this key to authenticate the agent’s callbacks (e.g.ntro_task_get).
4. Reference from a runbook step
From any@ui_step method:
input as its kickoff user message (JSON-serialised for dicts), runs to terminal status, and emits any output files. The Ntropii adapter handles the rest.
File output
The agent writes generated files to/mnt/session/outputs/<filename> — Anthropic’s runtime auto-promotes that path into the session’s file list. The Ntropii adapter:
- Polls the Anthropic Sessions API until the session is
terminated. - Lists session files via
GET /v1/files?scope_id=<session_id>(with backoff for the index-eventual-consistency race). - Downloads each file’s bytes.
- Persists to
ingest.submitted_documentswithsource = 'agent_output:<ntropii-agent-id>'.
Reference implementation
Theclaude-managed-agents repo on GitHub contains the production-ready definitions and integration spec:
audit-handover as the template for your own Managed Agents.
Related
Register agents
Generic registration flow, lifecycle, and reference table.
ntro.workflow.agents reference
invoke() signature, AgentResult shape, adapter polling + backoff semantics.Build runbooks
The runbook-side of invoking an agent inside a
@ui_step.Anthropic Managed Agents docs
Anthropic’s reference for Agents, Environments, Vaults, and Sessions.