Follow Discord
Sweep 28 Sep 2026 · 18:16Z Build v2.1.284 505 read Stable v2.1.277 Latest v2.1.284 Next v2.1.284 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.284 ·

Sandboxed commands on Linux start even with very large sandbox settings

On Linux, a sandbox setup too long for one command line is now passed to bubblewrap through a temporary file, with clear errors when it can't be

You'll notice Bug Fixes
JSON All of v2.1.284
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
SandboxArea: what it touches
Bug FixesKind: in v2.1.284,
Bug FixesSection of the release
What

On Linux, Claude Code can run Bash commands in a sandbox, a restricted environment that limits which files and settings a command can reach. It builds the sandbox with a program called bubblewrap (bwrap), passing every rule as a command-line argument. Claude Code now checks how long that command line gets:

  • Too long: the arguments are written to an unnamed temporary file, in the temp folder or /dev/shm, and handed to bubblewrap from there.
  • Too many arguments: it stops with a specific error.
  • A path containing a NUL byte (an invisible character that cannot appear in arguments): it stops with an error saying so.
  • No unnamed file can be opened: it stops with an error saying so.
Why

A sandbox with many allowed or denied paths or environment variables could exceed the operating system's limit on argument length and fail to start. Those setups should now start, and when one can't, the error says why.

See this entry in the whole of v2.1.284 →

Feedback