{"version":"2.1.293","anchor":"cloud-session-creation-settings-forwarding-consent-reworked","canonical_anchor":"cloud-session-creation-settings-forwarding-consent-reworked","heading":"Cloud sessions now check consent before sending this machine's settings","tier":"use","area":"Cloud Sessions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/cloud-session-creation-settings-forwarding-consent-reworked","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Cloud sessions now check consent before sending this machine's settings\n\nWhether creating a cloud session sends your machine's settings now depends on several consent signals, with a notice step in the terminal\n\n**Unclear.** Exactly which combination of these choices causes settings to be sent.\n\n**What**\n\nA cloud session is a Claude Code session that runs on a remote machine instead of yours. With `--forward-home-settings`, Claude Code can send your machine's settings to it. The decision about whether a launch sends them is now worked out from several things:\n\n- Host consent: the consent the host gives\n\n- Your own flags: whether you switched forwarding on yourself\n\n- Stored choice: the value saved from before\n\n- Syncing: whether the project is synced\n\nWhen forwarding is on, a consent or notice step now runs in the terminal as the session is created. Before, the host's consent was passed straight through to the decision.\n\n**Why**\n\nThis changes when your machine's settings are sent to cloud sessions. If you rely on them arriving, or on them staying put, expect a prompt or notice at session creation.\n\n- Area: Cloud Sessions\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: yes"}