What
When claude --cloud syncs files from your machine into a running session, the agent is now given a list of the files that were updated in place and told to re-read any it had already read before editing them. The list is capped in length.
Details
- The companion list of files that were not written on your machine is now filtered to drop paths that did merge successfully, so it no longer names files that landed.
Evidence
Re-read any of them you had read before you edit them.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundle--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 --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 --cloud, on Use Claude Code on the web.
`--cloud` works with a single repository at a time. The task runs in the cloud while you continue working locally. The older `--remote` spelling still works as a deprecated alias for `--cloud`.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 --cloud, on Use Claude Code on the web.