跳转到内容

多智能体沙箱与工具

Each agent in a multi-agent setup can override the global sandbox and 工具 policy. This page covers per-agent configuration, precedence rules, and examples.

Auth is per-agent: each agent reads from its own agentDir auth store at ~/.openclaw/agents/<agentId>/agent/auth-profiles.json. Credentials are not shared between agents. Never reuse agentDir across agents. If you want to share creds, copy auth-profiles.json into the other agent’s agentDir.


Example 1: Personal + Restricted Family Agent

Section titled “Example 1: Personal + Restricted Family Agent”
{
"agents": {
"list": [
{
"id": "main",
"default": true,
"name": "Personal Assistant",
"workspace": "~/.openclaw/workspace",
"sandbox": { "mode": "off" }
},
{
"id": "family",
"name": "Family Bot",
"workspace": "~/.openclaw/workspace-family",
"sandbox": {
"mode": "all",
"scope": "agent"
},
"tools": {
"allow": ["read"],
"deny": ["exec", "write", "edit", "apply_patch", "process", "browser"]
}
}
]
},
"bindings": [
{
"agentId": "family",
"match": {
"provider": "whatsapp",
"accountId": "*",
"peer": {
"kind": "group",
}
}
}
]
}

Result:

  • main agent: Runs on host, full 工具 access
  • family agent: Runs in Docker (one container per agent), only read 工具

{
"agents": {
"list": [
{
"id": "personal",
"workspace": "~/.openclaw/workspace-personal",
"sandbox": { "mode": "off" }
},
{
"id": "work",
"workspace": "~/.openclaw/workspace-work",
"sandbox": {
"mode": "all",
"scope": "shared",
"workspaceRoot": "/tmp/work-sandboxes"
},
"tools": {
"allow": ["read", "write", "apply_patch", "exec"],
"deny": ["browser", "gateway", "discord"]
}
}
]
}
}

Example 2b: Global coding profile + messaging-only agent

Section titled “Example 2b: Global coding profile + messaging-only agent”
{
"tools": { "profile": "coding" },
"agents": {
"list": [
{
"id": "support",
"tools": { "profile": "messaging", "allow": ["slack"] }
}
]
}
}

Result:

  • default agents get coding tools
  • support agent is messaging-only (+ Slack 工具)

Example 3: Different 沙箱 Modes per Agent

Section titled “Example 3: Different 沙箱 Modes per Agent”
{
"agents": {
"defaults": {
"sandbox": {
"mode": "non-main", // Global default
"scope": "session"
}
},
"list": [
{
"id": "main",
"workspace": "~/.openclaw/workspace",
"sandbox": {
"mode": "off" // Override: main never sandboxed
}
},
{
"id": "public",
"workspace": "~/.openclaw/workspace-public",
"sandbox": {
"mode": "all", // Override: public always sandboxed
"scope": "agent"
},
"tools": {
"allow": ["read"],
"deny": ["exec", "write", "edit", "apply_patch"]
}
}
]
}
}

When both global (agents.defaults.*) and agent-specific (agents.list[].*) configs exist:

Agent-specific settings override global:

agents.list[].sandbox.mode > agents.defaults.sandbox.mode
agents.list[].sandbox.scope > agents.defaults.sandbox.scope
agents.list[].sandbox.workspaceRoot > agents.defaults.sandbox.workspaceRoot
agents.list[].sandbox.workspaceAccess > agents.defaults.sandbox.workspaceAccess
agents.list[].sandbox.docker.* > agents.defaults.sandbox.docker.*
agents.list[].sandbox.browser.* > agents.defaults.sandbox.browser.*
agents.list[].sandbox.prune.* > agents.defaults.sandbox.prune.*

Notes:

  • agents.list[].sandbox.{docker,browser,prune}.* overrides agents.defaults.sandbox.{docker,browser,prune}.* for that agent (ignored when sandbox scope resolves to "shared").

The filtering order is:

  1. Tool profile (tools.profile or agents.list[].tools.profile)
  2. Provider 工具 profile (tools.byProvider[provider].profile or agents.list[].tools.byProvider[provider].profile)
  3. Global 工具 policy (tools.allow / tools.deny)
  4. 提供商工具策略 (tools.byProvider[provider].allow/deny)
  5. 特定于代理的工具策略 (agents.list[].tools.allow/deny)
  6. 代理提供商策略 (agents.list[].tools.byProvider[provider].allow/deny)
  7. 沙箱工具策略 (tools.sandbox.toolsagents.list[].tools.sandbox.tools)
  8. 子代理工具策略 (tools.subagents.tools,如适用)

每一层级都可以进一步限制工具,但不能恢复在更早层级中被拒绝的工具。 如果设置了 agents.list[].tools.sandbox.tools,它将替换该代理的 tools.sandbox.tools。 如果设置了 agents.list[].tools.profile,它将覆盖该代理的 tools.profile。 提供商工具键接受 provider(例如 google-antigravity)或 provider/model(例如 openai/gpt-5.2)。

工具策略支持 group:* 简写,这些简写可以扩展为多个工具。有关完整列表,请参阅工具组

每个代理的提升覆盖 (agents.list[].tools.elevated) 可以进一步限制特定代理的提升执行。有关详细信息,请参阅提升模式


之前(单一代理):

{
"agents": {
"defaults": {
"workspace": "~/.openclaw/workspace",
"sandbox": {
"mode": "non-main"
}
}
},
"tools": {
"sandbox": {
"tools": {
"allow": ["read", "write", "apply_patch", "exec"],
"deny": []
}
}
}
}

之后(具有不同配置文件的多代理):

{
"agents": {
"list": [
{
"id": "main",
"default": true,
"workspace": "~/.openclaw/workspace",
"sandbox": { "mode": "off" }
}
]
}
}

旧版 agent.* 配置由 openclaw doctor 迁移;今后建议使用 agents.defaults + agents.list


{
"tools": {
"allow": ["read"],
"deny": ["exec", "write", "edit", "apply_patch", "process"]
}
}
{
"tools": {
"allow": ["read", "exec", "process"],
"deny": ["write", "edit", "apply_patch", "browser", "gateway"]
}
}
{
"tools": {
"sessions": { "visibility": "tree" },
"allow": ["sessions_list", "sessions_send", "sessions_history", "session_status"],
"deny": ["exec", "write", "edit", "apply_patch", "read", "browser"]
}
}

agents.defaults.sandbox.mode: "non-main" 基于 session.mainKey(默认 "main"), 而不是代理 ID。群组/渠道会话总是获取自己的密钥,因此 它们被视为非主会话并将被沙箱隔离。如果您希望代理永不 沙箱隔离,请设置 agents.list[].sandbox.mode: "off"


配置多代理沙箱和工具后:

  1. 检查代理解析:

    openclaw agents list --bindings
  2. 验证沙箱容器:

    docker ps --filter "name=openclaw-sbx-"
  3. 测试工具限制:

    • 发送需要受限工具的消息
    • 验证代理无法使用被拒绝的工具
  4. 监控日志:

    tail -f "${OPENCLAW_STATE_DIR:-$HOME/.openclaw}/logs/gateway.log" | grep -E "routing|sandbox|tools"

尽管有 mode: "all",代理仍未进行沙箱隔离

Section titled “尽管有 mode: "all",代理仍未进行沙箱隔离”
  • 检查是否存在覆盖它的全局 agents.defaults.sandbox.mode
  • 代理特定配置具有优先权,因此请设置 agents.list[].sandbox.mode: "all"

尽管有拒绝列表,工具仍然可用

Section titled “尽管有拒绝列表,工具仍然可用”
  • 检查工具过滤顺序:全局 → 代理 → 沙箱 → 子代理
  • 每个级别只能进一步限制,不能恢复权限
  • 使用日志验证:[tools] filtering tools for agent:${agentId}
  • 在代理特定的沙箱配置中设置 scope: "agent"
  • 默认为 "session",它为每个会话创建一个容器