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
HomeReleasesv2.1.307entry #106

Claude Code v2.1.307 ·

Your BUN_OPTIONS value is now passed on to child processes from more places

Processes Claude Code starts now keep your BUN_OPTIONS value from the process, settings or system environment, still after --install=disable

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

Unclear Which value wins when BUN_OPTIONS is set in more than one of these places is not known.

What

BUN_OPTIONS is an environment variable, a named setting a program reads when it starts, that passes options to Bun. When Claude Code starts another Bun process, it builds that process's BUN_OPTIONS with --install=disable first. It now looks for your own value in three places:

  • The new process's own environment.
  • The env section of your Claude Code settings.
  • The environment Claude Code itself was started with.

Before, only the value from the settings env section was added.

Why

A BUN_OPTIONS value you set outside Claude Code's settings can now reach the processes it starts.

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 doubtWhich value wins when `BUN_OPTIONS` is set in more than one of these places is not known.

See this entry in the whole of v2.1.307 →

Feedback