openclaw - 💡(How to fix) Fix Per-agent tools.fs.workspaceOnly configuration — does it work in v2026.4.29? [1 comments, 2 participants]

Version: OpenClaw v2026.4.29 (macOS, Node v24)

What I'm trying to do: We have a multi-agent setup:

• One main agent (handles primary user interactions)
• Two sub-agents (specialized roles, more restricted)

We want the main agent to have full filesystem access (able to write anywhere on the host), while the sub-agents remain restricted to their own workspaces.

What I've tried:

• Set tools.fs.workspaceOnly: true globally, which correctly restricts all agents
• Added per-agent overrides for the main agent:

"agents": {
  "list": [
    {
      "id": "main",
      "tools": { "fs": { "workspaceOnly": false } }
    },
    {
      "id": "agent-1",
      "tools": { "fs": { "workspaceOnly": true } }
    },
    {
      "id": "agent-2", 
      "tools": { "fs": { "workspaceOnly": true } }
    }
  ]
}

Schema validation: openclaw config schema shows agents.list[].tools.fs.workspaceOnly is a valid config path in the schema.

Concern from prior issues: I found several reports from April 2026 (#31716, #29817, #30927) indicating that tools.fs.workspaceOnly: false was not working as expected — the write/edit tools were silently enforcing workspace-only regardless of the config value due to a bug in the implementation layer (createHostWriteOperations always calling toRelativePathInRoot).

Questions:

1. Is per-agent workspaceOnly override working correctly in v2026.4.29, or are the April 2026 bugs still present?
2. Is this the correct approach for giving one agent full filesystem access while keeping others restricted?
3. Any alternative approaches you'd recommend?