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.305 ·

Shell commands can set Bun options and refuse to run if they cannot

Claude Code can now set BUN_OPTIONS before shell commands to stop Bun auto-installing packages, and skips the command with exit code 126 if it cannot

Under the hood Internal Changes
JSON All of v2.1.305
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
Internal ChangesKind: in v2.1.305,
Internal ChangesSection of the release

Unclear It is not clear what turns on the new BUN_OPTIONS handling, so it is not clear which users get it.

What

Bun is a program that runs JavaScript, and BUN_OPTIONS is an environment variable (a named value a program reads when it starts) that passes it extra options. Claude Code can now set BUN_OPTIONS before running a shell command, to turn off Bun's automatic package installs.

  • If it cannot set BUN_OPTIONS, the command is not run. It stops with exit code 126 and the message "Claude Code did not run this command: it could not set BUN_OPTIONS".
  • When CLAUDE_CODE_REMOTE is set, the existing step that adds --smol to BUN_OPTIONS now uses the shell's built-in export, so a custom export in your shell setup cannot replace it.
Why

Shell commands run through Claude Code can now fail with exit code 126 if something in your shell environment stops BUN_OPTIONS from being set.

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 turns on the new `BUN_OPTIONS` handling, so it is not clear which users get it.

See this entry in the whole of v2.1.305 →

Feedback