Sandbox can't write to durable files
✅Solved
After the latest update and implementing the new sandbox rules, my Openclaw can't write to canonical durable files any more like workspace/AGENTS.md
It says it wrote it, but then it writes it only in the sandboxed folder that it's running in.
Makes me want to just turn off the sandbox feature.
Is there something I'm missing? I don't want to be falsely led into thinking that canonical durable files are being edited only to find out they weren't.
It says it wrote it, but then it writes it only in the sandboxed folder that it's running in.
Makes me want to just turn off the sandbox feature.
Is there something I'm missing? I don't want to be falsely led into thinking that canonical durable files are being edited only to find out they weren't.
Solution
If it’s truly just you, you can turn sandboxing off — but I’d only do that if you’re comfortable with “LLM mistakes now happen on the host” (especially
The nicer middle-ground is: keep sandboxing, but let the sandbox mount the real workspace so edits to
Recommended: keep
This keeps the “Discord threads are sandboxed” safety model, but makes writes persist:
Docs: https://docs.openclaw.ai/gateway/sandboxing (Workspace access)
execThe nicer middle-ground is: keep sandboxing, but let the sandbox mount the real workspace so edits to
AGENTS.mdRecommended: keep mode: "non-main"
, set workspaceAccess: "rw"
This keeps the “Discord threads are sandboxed” safety model, but makes writes persist:mode: "non-main"workspaceAccess: "rw"Docs: https://docs.openclaw.ai/gateway/sandboxing (Workspace access)
If you want the old behavior everywhere (no sandbox at all)
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
Recent Announcements
Similar Threads
Was this page helpful?
