{"version":"2.1.288","anchor":"cloud-sessions-refuse-to-change-claude-code-settings-files","canonical_anchor":"cloud-sessions-refuse-to-change-claude-code-settings-files","heading":"Cloud sessions now refuse clearly when asked to change settings files","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/cloud-sessions-refuse-to-change-claude-code-settings-files","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Cloud sessions now refuse clearly when asked to change settings files\n\nA cloud session asked to change its Claude Code settings files now tells Claude nothing was changed and that you must do it yourself\n\n**Unclear.** It is not clear which sessions or targets produce this refusal.\n\n**What**\n\nWhen a cloud session (Claude Code running on a remote machine instead of your own) is asked to change its Claude Code settings files, Claude now receives a message saying the session is not allowed to. The message says nothing was changed and that you need to make those changes on the named target yourself.\n\nClaude Code can also now describe why something stopped, with phrases such as \"when its call ended\" and \"at its time limit\".\n\n**Why**\n\nInstead of a settings edit failing silently or partly, you get a plain refusal and know to make the change yourself.\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"}