{"version":"2.1.300","anchor":"settings-writes-in-disklesscloud-sessions-go-through-storag","canonical_anchor":"settings-writes-in-disklesscloud-sessions-go-through-storag","heading":"Sessions that don't save settings to disk now store them another way","tier":"internal","area":"Diskless Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/settings-writes-in-disklesscloud-sessions-go-through-storag","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Sessions that don't save settings to disk now store them another way\n\nIn sessions that don't write settings to disk, Claude Code saves settings through a separate store and refuses changes that would make them too large\n\n**Unclear.** Which sessions count as not writing settings to disk is not stated.\n\n**What**\n\nSome sessions, such as cloud sessions, do not write settings to files on disk. When Claude Code saves a settings change in one of these sessions, it now:\n\n- Refuses to write the settings file to disk, with the message \"This session does not write settings to disk\"\n\n- Reads your current settings from a separate storage system instead of from the file\n\n- Refuses a change that would make your saved settings too big, with the message \"Your saved settings would be too large after this change, so the change was not saved\"\n\nBefore, settings were always written to disk.\n\n**Why**\n\nThis changes how settings are kept in sessions without a disk. If you see the size message, your change was not saved, and you need to make your settings smaller before trying again.\n\n- Area: Diskless Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}