What probably matters to youSection of the release
What
Before asking whether to sync your checkout to a cloud session, Claude Code now measures the repository and picks between starting from a remote ref, uploading a bundle, or deferring. Every refusal now comes with a stated reason. Bundle upload itself is gated by a server flag with no built-in default, so it is off unless the server enables it; CCR_ENABLE_BUNDLE=true forces it on locally and CCR_FORCE_BUNDLE skips remote detection.
Details
The probe measures pack size via pack-objects --revs --stdout --thin, the byte count of changed tracked files, and a survey of untracked files.
Written refusal reasons include: repository has no commits yet, a merge or cherry-pick is in progress, the workspace is untrusted, the index has unmerged entries, the remote is a self-hosted pool, the host is not GitHub, the repository is too large, and the platform is unsupported.
A new telemetry event records the outcome, the forecast, the host, how far the checkout has diverged, and byte counts.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added sinceA small documentation edit on Environment variables touched a line naming CCR_FORCE_BUNDLE after this was published.| `CCR_FORCE_BUNDLE` | Set to `1` to force [`claude --cloud`](/docs/en/claude-code-on-the-web#send-local-repositories-without-github) to bundle and upload your local repository instead of cloning from its remote |env-varssee the edit
Confirmed sinceAnthropic's documentation has since written up CCR_FORCE_BUNDLE, on Use Claude Code on the web.To upload a bundle even when Claude Code would otherwise clone from the remote, set `CCR_FORCE_BUNDLE=1`:claude-code-on-the-websee the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up CCR_FORCE_BUNDLE, on Use Claude Code on the web.