{"version":"2.1.314","anchor":"cloud-sessions-explain-why-settings-file-edits-are-not-appli","canonical_anchor":"cloud-sessions-explain-why-settings-file-edits-are-not-appli","heading":"Staged edit message now varies, and cloud sessions explain settings edits are not applied","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/cloud-sessions-explain-why-settings-file-edits-are-not-appli","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Staged edit message now varies, and cloud sessions explain settings edits are not applied\n\nThe message for staged edits now depends on stagedWording, so cloud sessions say settings-file edits were not applied and to make them elsewhere\n\n**What**\n\nSometimes Claude Code does not apply an edit straight away and instead holds it as a staged edit. The message shown for these edits used to be one fixed text for every kind of session. It now depends on a `stagedWording` value.\n\nIn a cloud session (a session running on remote servers rather than your own computer), an edit to a settings file now shows: \"Not applied \u00b7 a cloud session can't apply Claude's edits to settings files \u00b7 if you want this change, make it outside this session\".\n\n**Why**\n\nIn a cloud session you now get a clear reason why a settings change did not take effect and what to do about it, instead of a staged-edit message that did not fit the situation.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}