Claude Code v2.1.280 · 22 Sep 2026
Windows-specific env vars added to the host-passthrough allowlist
More environment variables, including Windows-specific ones, now pass through to Claude Code
Under the hood Tier: how much it should matter to you
1 Useful: my rating, 1 to 5
1 Signal: worth watching, 1 to 5
Windows Area: what it touches
Internal Changes Kind: in v2.1.280, 22 Sep 26
Internal Changes Section of the release
What
Claude Code now allows more environment variables through to itself:
CCR_FORCE_BUNDLE is documented as forcing claude --cloud to bundle and upload your local repository instead of cloning it from its remote.
Why
The 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.
See this entry in the whole of v2.1.280 →
22 Sep 2026 · 602 entries, this one is #559.
Use it now37 You'll notice196 Nothing to try yet22 Under the hood347
Open the release →
Names in this entry
env HOMEDRIVE More environment variables, including Windows-specific ones, now pass through to Claude Code
env HOMEPATH More environment variables, including Windows-specific ones, now pass through to Claude Code
env PROGRAMDATA More environment variables, including Windows-specific ones, now pass through to Claude Code
env CCR_ENABLE_BUNDLE Cloud sync sizes up your repo first and always tells you why it declined; bundle upload is server-gated.
env CCR_FORCE_BUNDLE Set to 1 to force claude --cloud to bundle and upload your local repository instead of cloning from its remote
env CLAUDE_CODE_DIR_SYNC_CHAIN A new 'chained' directory-sync mode exists behind an undocumented CLAUDE_CODE_DIR_SYNC_CHAIN env var
cli --cloud With a task description, create a new cloud session . With a session ID (session_... or cse_...) or a claude.ai/code URL, queue a message into that existing session instead, with -p. See send a follow-up message .
Is this right?
0
0
Feedback
What's wrong with this entry?
Hard to understand Too vague Looks wrong Not relevant to me Too long Missing the detail I wanted Duplicate of another card
Clear Learned something new I can act on this Good catch
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
← Previous · 558 of 602
correctionAttachment added to REPL/tool routing
Under the hood Tool Routing
In v2.1.280 Internal Changes release-page order
Next → · 560 of 602
Windows-path safety check now returns a reason code instead of a boolean
Under the hood Windows