{"version":"2.1.286","anchor":"cloud-settings-sync-description-reworded","canonical_anchor":"cloud-settings-sync-description-reworded","heading":"Clearer wording on which permission rules claude --cloud sends","tier":"notice","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/cloud-settings-sync-description-reworded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Clearer wording on which permission rules `claude --cloud` sends\n\nThe `claude --cloud` settings-sync text now says it sends your portable permission rules and shows on each launch whether they were sent\n\n**Unclear.** It is not clear whether what the sync actually sends changed, or only its description.\n\n**What**\n\n`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:\n\n- deny and ask rules can go along with the paths they name\n\n- rules about files need a path starting with `~\/` or a relative path\n\n- each launch shows whether the rules were sent\n\nBefore, the text said it sent only rules that don't name paths on this machine, and that each launch tells you what it sent.\n\n**Why**\n\nThe 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.\n\n- Area: Cloud Sessions\n- Names: `claude --cloud`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}