claude --cloud starts a session that runs in the cloud rather than on your machine, and it can take some of your settings with it. The text describing that settings sync has changed. It now says it sends "your portable permission rules". Permission rules are the settings that allow, ask about or deny actions. The text also explains:
- deny and ask rules can go along with the paths they name
- rules about files need a path starting with
~/or a relative path - each launch shows whether the rules were sent
Before, the text said it sent only rules that don't name paths on this machine, and that each launch tells you what it sent.
The new wording suggests rules that name paths may now travel to cloud sessions, as long as the path is written portably. What changed here is the description text.
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.
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
It is not clear whether what the sync actually sends changed, or only its description.
Anthropic's documentation has since written up claude --cloud, on Use Claude Code in the cloud.