What
Before offering file sync for a checkout, claude --cloud now checks the repository layout and holds the offer back when the layout is not one it can serve, rather than going on to forecast what it would bundle.
Details
- The deferral is recorded with the reason
layout_unserved. - The "not offered" line now also covers cases where paths cannot be resolved.
Evidence
layout_unserved
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundleclaude --cloud
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 since
A small documentation edit on Environment variables touched a line naming claude --cloud 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-vars see the edit
Confirmed since
Anthropic's documentation has since written up claude --cloud, on Use Claude Code on the web.
When you run `claude --cloud` from a repository that has no git remote, or from a github.com repository that the Claude GitHub App isn't installed on, Claude Code bundles your local repository and uploads it directly to the cloud session. …claude-code-on-the-web see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up claude --cloud, on Use Claude Code on the web.