{"version":"2.1.246","anchor":"forwarding-your-home-settings-to-a-cloud-session-now-records","canonical_anchor":"forwarding-your-home-settings-to-a-cloud-session-now-records","heading":"Forwarding your home settings to a cloud session now records explicit consent","tier":"use","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/forwarding-your-home-settings-to-a-cloud-session-now-records","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Forwarding your home settings to a cloud session now records explicit consent\n\nForwarding your home settings to a cloud session now records your consent separately from permission.\n\n**What**\n\n`--forward-home-settings` (used with `--cloud` or `--environment`) no longer just flips a boolean. Startup resolves a consent value and passes it through to session creation, so the fact that you consented is tracked separately from whether forwarding is allowed at all, and a settings-upload status feed now sits alongside the existing file-sync one.\n\n**Details**\n\n- Consent is carried into the create call and reported in telemetry as `home_settings_host_consent`; the created session's permission mode is echoed back.\n- A new refusal reason covers sessions \"launched from your home directory (or above it, or inside a checkout rooted there)\", which cannot be bound.\n- The launch options dropped a settings-plan wait timeout in favour of the consent value, and the consent-surface check can now be short-circuited by the host's answer.\n\n**Evidence**\n\n`home_settings_host_consent`, `homeSettingsConsent`, `replaceHomeSettingsHostConsent`, `launched from your home directory (or above it, or inside a checkout rooted there)`\n\n- Area: Cloud Sessions\n- Names: `--forward-home-settings`, `--cloud`, `--environment`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5"}