managed-agent
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseManaged Agent (Anthropic cloud runtime)
托管Agent(Anthropic云端运行时)
ruflo-agent| Runtime | Tools | Use it when |
|---|---|---|
WASM (local, | | fast, free, ephemeral, offline, untrusted code in a sandbox |
| Managed (Anthropic cloud) | | long-running / async work (minutes–hours), a real cloud container with pre-installed packages + network, persistent filesystem + transcript across turns |
This skill drives the managed runtime — Anthropic's Claude Managed Agents (beta). The model: Agent (model + system + tools + MCP servers + skills) → Environment (container template) → Session (running instance) → Events (turns / tool-use / status, persisted server-side). See and project ADR-115.
docs/adr/0001-wasm-contract.mdruflo-agent| Runtime | Tools | 适用场景 |
|---|---|---|
WASM(本地, | | 快速、免费、临时、离线运行,可在沙箱中处理不可信代码 |
| Managed(Anthropic云端) | | 长时间/异步任务(数分钟至数小时),具备预装软件包与网络能力的真实云端容器,跨轮次持久化文件系统与对话记录 |
本技能用于驱动托管运行时——Anthropic的Claude托管Agent(测试版)。模型架构:Agent(模型+系统配置+工具+MCP服务器+技能)→ Environment(容器模板)→ Session(运行实例)→ Events(对话轮次/工具调用/状态,服务器端持久化)。详见与项目ADR-115。
docs/adr/0001-wasm-contract.mdPrerequisites
前置条件
- (or
ANTHROPIC_API_KEY) in the environment, with Claude Managed Agents beta access.CLAUDE_API_KEY - If absent, every tool returns a structured "use
managed_agent_*for a local no-key runtime" error — fall back to the WASM skill.wasm_agent_create
- 环境中需配置(或
ANTHROPIC_API_KEY),且拥有Claude托管Agent测试版访问权限。CLAUDE_API_KEY - 若未配置,所有工具将返回结构化错误提示“使用
managed_agent_*启动无需密钥的本地运行时”,并自动回退至WASM技能。wasm_agent_create
Steps
操作步骤
-
Create —
mcp__claude-flow__managed_agent_create→{ model?, system?, name?, networking?, packages?, initScript?, mcpServers?, skills? }. Provisions Agent + Environment + Session. Save the three ids.{ sessionId, agentId, environmentId, status }- :
mcpServers— the cloud agent must be able to reach the URL. A local[{type:"url", url, name, authorization_token?}]is not reachable from Anthropic's cloud; deploy/tunnel an HTTP ruflo MCP server first if you want the cloud agent to have ruflo's tools.ruflo mcp start - :
packages— installed in the container.{pip?:[], npm?:[], apt?:[], cargo?:[], gem?:[], go?:[]}
-
Prompt —
mcp__claude-flow__managed_agent_prompt→ sends a user turn, polls the event log until the session goes idle (default 180s, capped 600s) →{ sessionId, message, maxWaitMs? }. For very long tasks, raise{ finished, status, stopReason, assistantText, toolUses[], eventCount }or follow up withmaxWaitMs.managed_agent_events -
Inspect —
mcp__claude-flow__managed_agent_status(idle/running/error) ·{ sessionId }mcp__claude-flow__managed_agent_events(full transcript: user turns, agent thinking, tool_use, tool_result, status — the cloud counterpart of{ sessionId, raw? }).wasm_agent_files -
List —
mcp__claude-flow__managed_agent_list— every session on the org (so you can see which are still running / billing).{ limit? } -
Terminate —
mcp__claude-flow__managed_agent_terminate— always do this when done: a cloud session keeps billing container time + tokens until deleted. Pass{ sessionId, environmentId? }to also delete the environment ruflo created.environmentId
-
创建 —
mcp__claude-flow__managed_agent_create→{ model?, system?, name?, networking?, packages?, initScript?, mcpServers?, skills? }。完成Agent、Environment与Session的部署。请保存这三个ID。{ sessionId, agentId, environmentId, status }- :
mcpServers— 云端Agent必须能够访问该URL。本地启动的[{type:"url", url, name, authorization_token?}]无法被Anthropic云端访问;若需让云端Agent使用ruflo工具,请先部署或通过隧道暴露HTTP版ruflo MCP服务器。ruflo mcp start - :
packages— 将在容器中安装的软件包。{pip?:[], npm?:[], apt?:[], cargo?:[], gem?:[], go?:[]}
-
发起提示 —
mcp__claude-flow__managed_agent_prompt→ 发送用户对话轮次,轮询事件日志直至Session进入空闲状态(默认180秒,上限600秒)→{ sessionId, message, maxWaitMs? }。对于超长任务,可提高{ finished, status, stopReason, assistantText, toolUses[], eventCount }或后续使用maxWaitMs跟进。managed_agent_events -
检查状态 —
mcp__claude-flow__managed_agent_status(返回idle/running/error状态)·{ sessionId }mcp__claude-flow__managed_agent_events(完整对话记录:用户轮次、Agent思考过程、tool_use、tool_result、状态——对应本地{ sessionId, raw? }的云端版本)。wasm_agent_files -
列出会话 —
mcp__claude-flow__managed_agent_list— 列出组织下所有会话(可查看哪些会话仍在运行/计费)。{ limit? } -
终止会话 —
mcp__claude-flow__managed_agent_terminate— 完成任务后务必执行此操作:云端会话会持续产生容器时长与令牌费用,直至删除。传入{ sessionId, environmentId? }可同时删除ruflo创建的环境。environmentId
Cost & safety
成本与安全
- Managed Agents bill per session (LM tokens + container time) and are rate-limited per org. Estimate before a long run; record completed sessions to the namespace.
cost-tracking - Treat orphaned sessions like leaked resources — then
managed_agent_listanything stale.managed_agent_terminate - Beta API ();
managed-agents-2026-04-01/multiagenton the agent config are research preview.define-outcomes
- 托管Agent按会话计费(包含大模型令牌费用+容器时长),且按组织设置速率限制。执行长任务前请估算成本;将已完成会话记录至命名空间。
cost-tracking - 孤立会话视为资源泄漏——使用列出会话,再用
managed_agent_list清理过期会话。managed_agent_terminate - 测试版API();Agent配置中的
managed-agents-2026-04-01/multiagent为研究预览功能。define-outcomes
Quick example
快速示例
managed_agent_create { "model": "claude-haiku-4-5-20251001", "system": "Terse. Do exactly what is asked.", "name": "scratch" }
→ { sessionId: "sesn_…", agentId: "agent_…", environmentId: "env_…", status: "idle" }
managed_agent_prompt { "sessionId": "sesn_…", "message": "echo hello > /tmp/x && cat /tmp/x — then stop." , "maxWaitMs": 60000 }
→ { finished: true, status: "idle", stopReason: "end_turn", assistantText: "Done.", toolUses: [{name:"bash", input:{command:"echo hello > /tmp/x && cat /tmp/x"}}] }
managed_agent_terminate { "sessionId": "sesn_…", "environmentId": "env_…" }
→ { sessionDeleted: true, environmentDeleted: true }managed_agent_create { "model": "claude-haiku-4-5-20251001", "system": "Terse. Do exactly what is asked.", "name": "scratch" }
→ { sessionId: "sesn_…", agentId: "agent_…", environmentId: "env_…", status: "idle" }
managed_agent_prompt { "sessionId": "sesn_…", "message": "echo hello > /tmp/x && cat /tmp/x — then stop." , "maxWaitMs": 60000 }
→ { finished: true, status: "idle", stopReason: "end_turn", assistantText: "Done.", toolUses: [{name:"bash", input:{command:"echo hello > /tmp/x && cat /tmp/x"}}] }
managed_agent_terminate { "sessionId": "sesn_…", "environmentId": "env_…" }
→ { sessionDeleted: true, environmentDeleted: true }