Starting a remote or teleported session can now seed the environment from a local git bundle instead of a full sync, behind new flags
What
When starting a cloud/bridge (teleport) session, Claude Code can now seed the remote environment from a local git bundle instead of doing a full sync.
- Whether to enable bundle seeding is controlled by the
tengu_ccr_bundle_seed_enabledgate or theCCR_ENABLE_BUNDLEenvironment variable, and is off by default unless forced. - The
CCR_FORCE_BUNDLEenvironment variable can force bundling of the workspace regardless of the gate. - These combine into an internal
allowBundledecision that determines whether a git bundle is uploaded to seed the remote environment.
Why
Seeding from a git bundle can be faster or more reliable than a full sync when setting up a remote session, while the gate and env vars let this be rolled out and forced on selectively.
tengu_ccr_bundle_seed_enabled Gate removed from the codeThis release deleted the gate from the code while it was still reading on for the account this site reads, so the code path no longer asks a flag before running.
This account: on · anonymous baseline: on · compiled default in v2.1.273: not a boolean we can read
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.273. It isn't a statement about your account. What a flag value here can and cannot tell you
The code path no longer asks a flag before it runs.
The code path no longer asks a flag before it runs.
The code path no longer asks a flag before it runs.
The code path no longer asks a flag before it runs.
The code path no longer asks a flag before it runs.