{"version":"2.1.288","anchor":"cloud-home-settings-seed-prompt-handles-not-stored","canonical_anchor":"cloud-home-settings-seed-prompt-handles-not-stored","heading":"Cloud session settings prompt now reports a separate not-stored outcome","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/cloud-home-settings-seed-prompt-handles-not-stored","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Cloud session settings prompt now reports a separate not-stored outcome\n\nThe prompt that seeds your home settings into a cloud session now tells apart four outcomes, including a new not-stored case\n\n**Unclear.** It is not clear what leads to the not-stored outcome or what you see when it happens.\n\n**What**\n\nIn a cloud session, Claude Code can offer to seed your home settings, which means copying your usual settings into the cloud environment. The step that handles your answer used to recognise only two outcomes. It now recognises four:\n\n- refused\n\n- not stored, which is the new case\n\n- unconfirmed\n\n- written\n\n**Why**\n\nA cloud session can now report that the settings were not stored, instead of folding that result into one of the other outcomes.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}