Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.304 ·

allowAllUnixSockets description warns it also opens VM sockets on Linux

The allowAllUnixSockets sandbox setting is now described as also unblocking VM sockets (AF_VSOCK) on Linux

You'll notice Improvements
JSON All of v2.1.304
You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
SandboxArea: what it touches
ImprovementsKind: in v2.1.304,
ImprovementsSection of the release
What

The sandbox setting allowAllUnixSockets lets sandboxed commands use any Unix socket, a channel programs on the same machine use to talk to each other. Its description now adds that on Linux it also unblocks VM sockets (AF_VSOCK), which let a virtual machine talk to the machine hosting it.

Why

Turning this setting on opens more than its name suggests on Linux, so weigh that before enabling it.

Read from
Names in the bundleallowAllUnixSockets
What the documentation says
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Confirmed since Anthropic's documentation has since written up allowAllUnixSockets, on Configure the sandboxed Bash tool. * `unshare -U true` prints `unshare: unshare failed: Operation not permitted`. With [`allowAllUnixSockets`](/docs/en/settings-reference#sandbox-network-allowallunixsockets) on, it can print `No space left on device` instead sandboxing see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up allowAllUnixSockets, on Configure the sandboxed Bash tool.

See this entry in the whole of v2.1.304 →

Feedback