From ce2cf57de091ae7f16a71a295ed01ecf1a78c983 Mon Sep 17 00:00:00 2001 From: David Karlsson <35727626+dvdksn@users.noreply.github.com> Date: Wed, 28 Oct 2026 07:35:27 +0000 Subject: [PATCH 1/2] docs: Document FUSE access controls for sandboxes The configuration references omit the controls for mounting FUSE filesystems. Document the global setting, environment opt-out, creation-only behavior, and backend restrictions. --- .../configuration/environment-files.md | 7 +++++++ .../ai/sandboxes/configuration/settings.md | 18 ++++++++++++++++++ 2 files changed, 25 insertions(+) diff --git a/content/manuals/ai/sandboxes/configuration/environment-files.md b/content/manuals/ai/sandboxes/configuration/environment-files.md index 5a5b32fefe5..ba82e540708 100644 --- a/content/manuals/ai/sandboxes/configuration/environment-files.md +++ b/content/manuals/ai/sandboxes/configuration/environment-files.md @@ -672,6 +672,7 @@ kits. Bindings take effect when the sandbox is created. | `profile` | string | None | Governance profile name | | `skills` | string | Daemon default | Shared agent skills store access: `off`, `readonly`, or `readwrite` | | `display` | boolean | `false` | Provision a display socket for graphical applications | +| `fuse` | boolean | `sandbox.fuse` setting | Mount FUSE filesystems; local only | | `gpu` | boolean | `false` | Pass the host GPU through to the sandbox | | `usb` | list of strings | None | USB device selectors to pass through to the sandbox | | `writableEnvFiles` | boolean | `false` | Let the sandbox write to shared environment files; local only | @@ -687,6 +688,12 @@ store. Set it to `off` to omit the mount, `readonly` to mount the store read-onl or `readwrite` to let the sandbox modify shared skills. If omitted, it uses the daemon's default, which is `readonly` unless your organization overrides it. +`fuse` inherits the [`sandbox.fuse`](settings.md#sandboxfuse) setting when +omitted. Set it to `false` to disable FUSE access for this sandbox. Setting it +to `true` cannot override `sandbox.fuse: false`. The option applies when the +sandbox is created; existing sandboxes retain their configuration. The +experimental Runtime backend and cloud sandboxes reject `fuse: true`. + ### `lifecycle` The `lifecycle` block declares commands that run on the host with your user diff --git a/content/manuals/ai/sandboxes/configuration/settings.md b/content/manuals/ai/sandboxes/configuration/settings.md index 6d57bd52564..b5a39b01540 100644 --- a/content/manuals/ai/sandboxes/configuration/settings.md +++ b/content/manuals/ai/sandboxes/configuration/settings.md @@ -198,6 +198,24 @@ permissions, outside the sandbox. Leave the setting at `false` to require approval on every invocation, or use `--force` to approve only one invocation. See [environment lifecycle commands](environment-files.md#lifecycle). +#### sandbox.fuse {.wrap-anywhere} + +{{< setting-metadata type="boolean" default="true" >}} + +Expose `/dev/fuse` and grant the `SYS_ADMIN` capability so processes can mount +FUSE filesystems in local sandboxes. Set this to `false` to disable FUSE access +for sandboxes you create: + +```console +$ sbx settings set sandbox.fuse false +``` + +Changes apply only to newly created sandboxes. Existing sandboxes retain their +FUSE configuration, including after restarts. To disable access for one sandbox, +set [`sandboxOptions.fuse`](environment-files.md#sandboxoptions) to `false` +in its environment file. FUSE is unsupported by the experimental Runtime +backend and cloud sandboxes. + #### ssh.agentForwardingEnabled {.wrap-anywhere} {{< setting-metadata type="boolean" default="true" >}} From df37b951e40b6817c437a8866e6948f482aef152 Mon Sep 17 00:00:00 2001 From: David Karlsson <35727626+dvdksn@users.noreply.github.com> Date: Wed, 28 Oct 2026 07:45:03 +0000 Subject: [PATCH 2/2] docs: Clarify FUSE configuration guidance The FUSE reference mentioned an unshipped backend and repeated settings behavior in the environment-file reference. Remove the backend mention and keep settings behavior in the settings reference, with a link from the environment option. --- .../ai/sandboxes/configuration/environment-files.md | 8 +++----- content/manuals/ai/sandboxes/configuration/settings.md | 4 ++-- 2 files changed, 5 insertions(+), 7 deletions(-) diff --git a/content/manuals/ai/sandboxes/configuration/environment-files.md b/content/manuals/ai/sandboxes/configuration/environment-files.md index ba82e540708..bbed4268ce5 100644 --- a/content/manuals/ai/sandboxes/configuration/environment-files.md +++ b/content/manuals/ai/sandboxes/configuration/environment-files.md @@ -688,11 +688,9 @@ store. Set it to `off` to omit the mount, `readonly` to mount the store read-onl or `readwrite` to let the sandbox modify shared skills. If omitted, it uses the daemon's default, which is `readonly` unless your organization overrides it. -`fuse` inherits the [`sandbox.fuse`](settings.md#sandboxfuse) setting when -omitted. Set it to `false` to disable FUSE access for this sandbox. Setting it -to `true` cannot override `sandbox.fuse: false`. The option applies when the -sandbox is created; existing sandboxes retain their configuration. The -experimental Runtime backend and cloud sandboxes reject `fuse: true`. +Set `fuse` to `false` to disable FUSE access for this sandbox. See the +[`sandbox.fuse` setting](settings.md#sandboxfuse) for defaults and when changes +take effect. ### `lifecycle` diff --git a/content/manuals/ai/sandboxes/configuration/settings.md b/content/manuals/ai/sandboxes/configuration/settings.md index b5a39b01540..1aa6d902b00 100644 --- a/content/manuals/ai/sandboxes/configuration/settings.md +++ b/content/manuals/ai/sandboxes/configuration/settings.md @@ -213,8 +213,8 @@ $ sbx settings set sandbox.fuse false Changes apply only to newly created sandboxes. Existing sandboxes retain their FUSE configuration, including after restarts. To disable access for one sandbox, set [`sandboxOptions.fuse`](environment-files.md#sandboxoptions) to `false` -in its environment file. FUSE is unsupported by the experimental Runtime -backend and cloud sandboxes. +in its environment file. When this setting is `false`, environment files cannot +enable FUSE access. Cloud sandboxes do not support FUSE. #### ssh.agentForwardingEnabled {.wrap-anywhere}