{"version":"2.1.265","anchor":"new-allowlist-forwards-bunmimalloc-gc-tuning-env-vars-only","canonical_anchor":"new-allowlist-forwards-bunmimalloc-gc-tuning-env-vars-only","heading":"New allowlist forwards Bun\/mimalloc GC tuning env vars only for remote sessions","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/new-allowlist-forwards-bunmimalloc-gc-tuning-env-vars-only","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### New allowlist forwards Bun\/mimalloc GC tuning env vars only for remote sessions\n\nRemote sessions now pass through Bun and mimalloc garbage-collection tuning environment variables to spawned processes\n\n**What**\n\nA new allowlist of environment variables related to memory management tuning is now forwarded to spawned processes, but only when `CLAUDE_CODE_REMOTE` is set to true. The variables are `BUN_GC_TIMER_INTERVAL`, `BUN_GC_TIMER_DISABLE`, `BUN_GC_RUNS_UNTIL_SKIP_RELEASE_ACCESS`, `BUN_IDLE_GC_SECONDS`, and `MIMALLOC_PURGE_HOLES_MIN_INTERVAL`. These control garbage collection (automatic memory cleanup) timing in Bun, the JavaScript runtime Claude Code uses, and in mimalloc, a memory allocator library.\n\n**Why**\n\nThis lets remote sessions be tuned for memory behavior via environment variables without affecting local sessions, which don't get these variables passed through.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}