{"version":"2.1.132","anchor":"custom-linux-sandbox-binary-paths","canonical_anchor":"custom-linux-sandbox-binary-paths","heading":"Custom Linux Sandbox Binary Paths","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.132\/e\/custom-linux-sandbox-binary-paths","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.132","markdown":"### Custom Linux Sandbox Binary Paths\n\n**What**\n\nLinux users can now configure exact `bwrap` and `socat` binary paths for sandbox and proxy bridge setup.\n\n**Usage**\n\n`{ \"sandbox\": { \"bwrapPath\": \"\/usr\/bin\/bwrap\", \"socatPath\": \"\/usr\/bin\/socat\" } }` **Details** - `bwrapPath` controls the bubblewrap executable used for Linux sandboxing. - `socatPath` controls the executable used for HTTP\/SOCKS bridge processes. - Claude Code validates that configured paths are executable and reports clearer errors if not. - This is useful on systems where these tools are installed outside `PATH`, or where a managed environment pins exact binary locations. **Evidence** Sandbox schema adds `bwrapPath` and `socatPath` settings (search for `\"Linux only: absolute path to the bwrap\"` and `\"Linux only: absolute path to the socat binary\"`)"}