{"version":"2.1.280","anchor":"windows-specific-env-vars-added-to-the-host-passthrough-allo","canonical_anchor":"windows-specific-env-vars-added-to-the-host-passthrough-allo","heading":"Windows-specific env vars added to the host-passthrough allowlist","tier":"internal","area":"Windows","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/windows-specific-env-vars-added-to-the-host-passthrough-allo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Windows-specific env vars added to the host-passthrough allowlist\n\nMore environment variables, including Windows-specific ones, now pass through to Claude Code\n\n**What**\n\nClaude Code now allows more environment variables through to itself:\n\n- `HOMEDRIVE`, `HOMEPATH`, and `PROGRAMDATA`, which help resolve credential and config paths on Windows\n\n- `CCR_ENABLE_BUNDLE`, `CCR_FORCE_BUNDLE`, and `CLAUDE_CODE_DIR_SYNC_CHAIN`, alongside existing directory-sync and legacy-bundle variables\n\n`CCR_FORCE_BUNDLE` is documented as forcing `claude --cloud` to bundle and upload your local repository instead of cloning it from its remote.\n\n**Why**\n\nThe Windows-specific variables improve how Claude Code finds config and credential paths on Windows. The `CCR_*` variables continue to support remote \"teleport\" sessions that seed a remote workspace from a local git bundle.\n\n- Area: Windows\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}