{"version":"2.1.301","anchor":"cloud-sessions-get-a-specific-not-applied-message-for-sett","canonical_anchor":"cloud-sessions-get-a-specific-not-applied-message-for-sett","heading":"Cloud sessions explain why Claude cannot change Claude Code's settings files","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/cloud-sessions-get-a-specific-not-applied-message-for-sett","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Cloud sessions explain why Claude cannot change Claude Code's settings files\n\nIn a cloud session, Claude is now told that settings-file edits need approval on the machine running Claude Code, and not to retry\n\n**What**\n\nWhen Claude tries to edit a Claude Code settings file and the edit is not applied, Claude Code tells the model why. There is now a separate message for cloud sessions, meaning sessions that run on a remote machine instead of your own computer.\n\nThe message says that a change to a Claude Code settings file only takes effect when a person approves it at the computer Claude Code runs on, and that a cloud session cannot take that approval. It also tells the model not to try the edit again.\n\n**Why**\n\nIn a cloud session, Claude now gets a clear reason why a settings edit did not go through and stops retrying it.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}