{"version":"2.1.321","anchor":"cloud-sessions-refuse-an-automode-block-instead-of-dropping","canonical_anchor":"cloud-sessions-refuse-an-automode-block-instead-of-dropping","heading":"Cloud sessions now refuse auto mode rules from settings files","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/cloud-sessions-refuse-an-automode-block-instead-of-dropping","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Cloud sessions now refuse auto mode rules from settings files\n\nA cloud session given an autoMode block through --settings or a repository's .claude\/settings.json now stops with an error\n\n**What**\n\nA cloud session is a Claude Code session that runs on remote machines rather than on your own computer. It does not accept your own auto mode rules, the allow and deny rules set in an `autoMode` block, from either of these:\n\n- the `--settings` option you pass when starting Claude Code\n\n- a repository's `.claude\/settings.json` file\n\nIf one of them contains an `autoMode` block, the session now refuses it with an error and tells you to start it without that block. Before, the block would be silently dropped.\n\n**Why**\n\nIf you keep `autoMode` rules in a repository's settings, a cloud session on that repository will now fail with an error instead of quietly ignoring them. Remove the block or keep it out of what the cloud session reads.\n\n- Area: Cloud Sessions\n- Names: `autoMode`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}