{"version":"2.1.288","anchor":"cloud-session-settings-change-refusal-now-tells-the-user-to","canonical_anchor":"cloud-session-settings-change-refusal-now-tells-the-user-to","heading":"Cloud sessions now say settings can only be changed on the host machine","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/cloud-session-settings-change-refusal-now-tells-the-user-to","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Cloud sessions now say settings can only be changed on the host machine\n\nWhen a cloud session blocks a command editing Claude Code settings, Claude now says to change them on the host instead of suggesting a workaround\n\n**Unclear.** It is not clear whether editing those settings files with Edit or Write is also blocked elsewhere.\n\n**What**\n\nIn a cloud session, Claude Code blocks a shell command that tries to change its settings files. The message Claude receives when this happens has changed.\n\nIt used to suggest making the change with the Edit or Write tools instead, where the change would be held until the session's owner reviewed it. It now tells Claude to let you know that those settings can only be changed on the host machine itself.\n\n**Why**\n\nClaude is no longer pointed at Edit or Write as a way around the block. If a setting needs changing for a cloud session, expect to change it yourself on the host machine.\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"}