{"version":"2.1.288","anchor":"cloud-session-settings-toggle-verifies-persistence-and-repor","canonical_anchor":"cloud-session-settings-toggle-verifies-persistence-and-repor","heading":"Cloud session setting changes are double-checked, with a clearer Windows file name error","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/cloud-session-settings-toggle-verifies-persistence-and-repor","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Cloud session setting changes are double-checked, with a clearer Windows file name error\n\nWhen a cloud session setting change is not confirmed, Claude Code rereads and retries it, and reports `not_stored` if it did not stick\n\n**What**\n\nWhen Claude Code changes a setting stored for cloud sessions and the change is not confirmed, it now reads the stored value back and tries again. If the value still did not stick, it reports `not_stored`. Before, it only reported that the change was unconfirmed.\n\nThere is also a new message for when your checkout (your local copy of the code) tracks file names that Windows cannot hold. It tells you to commit files by name.\n\n**Why**\n\nYou find out whether a setting actually saved, and uploading a cloud session from a checkout with Windows-incompatible file names gives you something you can act on.\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"}