Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.1.132 Home All releases olderv2.1.131 v2.1.133newer

Custom Linux Sandbox Binary Paths

What

Linux users can now configure exact bwrap and socat binary paths for sandbox and proxy bridge setup.

Usage
{
  "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")

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.

See this entry in the whole of v2.1.132 →