{"version":"2.1.319","anchor":"move-to-cloud-permission-mode-check-refactored","canonical_anchor":"move-to-cloud-permission-mode-check-refactored","heading":"Checks for keeping auto mode when moving to the cloud are grouped together","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/move-to-cloud-permission-mode-check-refactored","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Checks for keeping auto mode when moving to the cloud are grouped together\n\nThe reasons a session moved to the cloud may not keep auto mode are now worked out together, with no change in behaviour\n\n**What**\n\nWhen you move a session to the cloud, Claude Code decides whether to ask for auto mode to carry over. The reasons it would not are now worked out in one place and reported together: the remote kill switch is on, auto mode is off, or your settings cannot be read. The kill switch is still off unless it is switched on remotely.\n\n**Why**\n\nLittle changes for you, since the same conditions apply as before.\n\n- Flag `tengu_happy_ocean`: Off in both readings (read for one account on one subscription tier against v2.1.319; this account: off, anonymous baseline: off, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}