{"version":"2.1.293","anchor":"cloud-settings-restore-new-settings-gone-notice-and-crede","canonical_anchor":"cloud-settings-restore-new-settings-gone-notice-and-crede","heading":"Cloud sessions explain more clearly which settings were not carried over","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/cloud-settings-restore-new-settings-gone-notice-and-crede","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Cloud sessions explain more clearly which settings were not carried over\n\nCloud sessions now give a separate notice when forwarded settings are lost after the environment is recreated, and list rules left out for looking like credentials\n\n**What**\n\nIn a cloud session, Claude Code can carry over user settings forwarded from your machine and tells you what it could not restore. That notice changed:\n\n- A separate message now covers settings that are gone: \"This cloud environment was recreated, and any user settings forwarded from your machine are not in force here\".\n\n- The list of dropped rules now also names rules left out for looking like a credential, such as a password or key.\n\nClaude Code also counts how many restrictions and files were left out because they looked like credentials, and rewrites restored settings using a dedicated restore mode. It now works out once whether `CLAUDE_CODE_WORKER_EPOCH` is greater than 1 and uses that to decide whether part of this setup is enabled.\n\n**Why**\n\nYou get a more precise picture of what did and did not make it into a cloud session, including what was held back because it looked like a secret.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}