Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Diskless SessionsArea: what it touches
Internal ChangesKind: in v2.1.300,
Internal ChangesSection of the release
Unclear Which sessions count as not writing settings to disk is not stated.
What
Some 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:
Refuses to write the settings file to disk, with the message "This session does not write settings to disk"
Reads your current settings from a separate storage system instead of from the file
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"
Before, settings were always written to disk.
Why
This 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.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhich sessions count as not writing settings to disk is not stated.
