Custom Linux Sandbox Binary Paths#
What's wrong with this entry?
Linux users can now configure exact bwrap and socat binary paths for sandbox and proxy bridge setup.
{
"sandbox": {
"bwrapPath": "/usr/bin/bwrap",
"socatPath": "/usr/bin/socat"
}
}bwrapPathcontrols the bubblewrap executable used for Linux sandboxing.socatPathcontrols 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.
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")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.