`write` tool cannot write to folder outside OpenClaw workspace
✅Solved
I suddenly encountered an error from the
"Symlink escapes sandbox root"
The OpenClaw agent's workspace is:
~/.openclaw/workspace-permanent-memories
Under that workspace, there is this symlink:
~/.openclaw/workspace-permanent-memories/memory -> /mnt/user/Second-Brain/memory
This seems new since OpenClaw version 2026.2.26. Previously OpenClaw has written to the same memory directory without issues.
---
openclaw sandbox explain
OpenClaw 2026.2.26 (bc50708) — Say "stop" and I'll stop—say "ship" and we'll both learn a lesson.
Effective sandbox:
agentId: main
sessionKey: agent:main:main
mainSessionKey: agent:main:main
runtime: direct
mode: off scope: agent perSession: false
workspaceAccess: none workspaceRoot: /home/openclaw-user/.openclaw/sandboxes
Sandbox tool policy:
allow (default): exec, process, read, write, edit, apply_patch, image, sessions_list, sessions_history, sessions_send, sessions_spawn, subagents, session_status
deny (default): browser, canvas, nodes, cron, gateway, telegram, whatsapp, discord, irc, googlechat, slack, signal, imessage
Elevated:
enabled: true
channel: (unknown)
allowedByConfig: false
Fix-it:
- tools.sandbox.tools.allow
- tools.sandbox.tools.deny
- agents.list[].tools.sandbox.tools.allow
- agents.list[].tools.sandbox.tools.deny
- tools.elevated.enabled
Docs: docs.openclaw.ai/sandbox
openclaw config get tools.fs.workspaceOnly
OpenClaw 2026.2.26 (bc50708) — Welcome to the command line: where dreams compile and confidence segfaults.
Config path not found: tools.fs.workspaceOnly
openclaw --version
2026.2.26
write"Symlink escapes sandbox root"
The OpenClaw agent's workspace is:
~/.openclaw/workspace-permanent-memories
Under that workspace, there is this symlink:
~/.openclaw/workspace-permanent-memories/memory -> /mnt/user/Second-Brain/memory
This seems new since OpenClaw version 2026.2.26. Previously OpenClaw has written to the same memory directory without issues.
---
openclaw sandbox explain
OpenClaw 2026.2.26 (bc50708) — Say "stop" and I'll stop—say "ship" and we'll both learn a lesson.Effective sandbox:
agentId: main
sessionKey: agent:main:main
mainSessionKey: agent:main:main
runtime: direct
mode: off scope: agent perSession: false
workspaceAccess: none workspaceRoot: /home/openclaw-user/.openclaw/sandboxes
Sandbox tool policy:
allow (default): exec, process, read, write, edit, apply_patch, image, sessions_list, sessions_history, sessions_send, sessions_spawn, subagents, session_status
deny (default): browser, canvas, nodes, cron, gateway, telegram, whatsapp, discord, irc, googlechat, slack, signal, imessage
Elevated:
enabled: true
channel: (unknown)
allowedByConfig: false
Fix-it:
- tools.sandbox.tools.allow
- tools.sandbox.tools.deny
- agents.list[].tools.sandbox.tools.allow
- agents.list[].tools.sandbox.tools.deny
- tools.elevated.enabled
Docs: docs.openclaw.ai/sandbox
openclaw config get tools.fs.workspaceOnly
OpenClaw 2026.2.26 (bc50708) — Welcome to the command line: where dreams compile and confidence segfaults.Config path not found: tools.fs.workspaceOnly
openclaw --version
2026.2.26
Solution
Option B: /etc/fstab
bind mounts
Classic Linux approach, persists across reboots. Something like:/etc/fstab-
/mnt/user/Second-Brain/openclaw-memory/main /home/<user>/.openclaw/workspace/memory none bind 0 0(repeat for each workspace)
One quick caution
Even if you “don’t use”YYYY-MM-DD.mdIf you paste:
-
systemctl cat openclaw-gateway.service- and
ls -la ~/.openclaw/workspace*/memory…I can tell you which of the two approaches (systemd BindPaths vs fstab) will be less painful on your VM, and what exact paths to use.
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
131,281Members
Resources
Was this page helpful?
