You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
PluginsArea: what it touches
Internal ChangesKind: in v2.1.305,
ImprovementsSection of the release
Unclear It is not clear what these per-plugin options are or what they change.
What
Several changes landed in the code that starts shell commands and plugin commands.
bunOptionsFor is a new optional callback that builds Bun options from a filtered set of environment variables. Bun is the program that runs JavaScript for Claude Code. The callback is passed into the command builder and into the environment of the started command. The plugin command runner now supplies it keyed by plugin id, so each plugin's background commands can get their own Bun options.
In a sandbox (a restricted area that limits what a command can reach) using a strict file-system setup, allowNestedUserNamespaces is now set to false.
When a command fails to start and no process was created, Claude Code now shows a specific message if the disk is full: "The command was not started: this computer's disk is full". Before, this fell through to a generic error.
Why
If a command fails because your disk is full, you are now told that directly. Strict sandboxes are slightly tighter. The per-plugin Bun options mean background commands from different plugins may now start with different settings.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear what these per-plugin options are or what they change.
