Skip to content
BENIBIX Learn

sandbox.filesystem.allowWrite

AI⌨️ Claude CodeConfiguration

Also known as allowWrite

A list of more folders that fenced commands may write to.

Think of it like

It is like giving a child one more room to draw in.

Example

Emma's build writes to /tmp/build and fails in the sandbox. She adds that path to allowWrite, and the build works.

Why it matters

It opens just the one folder a tool needs. The rest of the fence stays up.

Definition

sandbox.filesystem.allowWrite is a settings key that opens more folders for writing. By default a fenced command may write only in a few spots. Those are the work folder, the temp folder and folders added with /add-dir. Add a path when a tool such as kubectl must write somewhere else. On Linux, the path must exist first.

Example code

json
{
  "sandbox": {
    "filesystem": {
      "allowWrite": ["~/.kube", "/tmp/build"]
    }
  }
}
Let kubectl and the build write outside the project.
Write is narrow, read is wide, and the four keys adjust both.

Common mistake

Adding a Linux path that does not exist yet. The entry does nothing until the folder is made.

Key takeaways

  1. 1
    Extra write paths. Beyond the project.
  2. 2
    Default is narrow. Project, temp.
  3. 3
    Linux: path must exist. Make it first.