{"version":"2.1.307","anchor":"bun-spawn-options-now-keep-a-users-bun-options-with-a-more","canonical_anchor":"bun-spawn-options-now-keep-a-users-bun-options-with-a-more","heading":"Your BUN_OPTIONS value is now passed on to child processes from more places","tier":"notice","area":"Environment Variables","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/bun-spawn-options-now-keep-a-users-bun-options-with-a-more","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Your `BUN_OPTIONS` value is now passed on to child processes from more places\n\nProcesses Claude Code starts now keep your `BUN_OPTIONS` value from the process, settings or system environment, still after `--install=disable`\n\n**Unclear.** Which value wins when `BUN_OPTIONS` is set in more than one of these places is not known.\n\n**What**\n\n`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:\n\n- The new process's own environment.\n\n- The `env` section of your Claude Code settings.\n\n- The environment Claude Code itself was started with.\n\nBefore, only the value from the settings `env` section was added.\n\n**Why**\n\nA `BUN_OPTIONS` value you set outside Claude Code's settings can now reach the processes it starts.\n\n- Area: Environment Variables\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}