You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Cloud SessionsArea: what it touches
ImprovementsKind: in v2.1.321,
ImprovementsSection of the release
What
A 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:
the --settings option you pass when starting Claude Code
a repository's .claude/settings.json file
If 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.
Why
If 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.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed sinceAnthropic's documentation has since written up autoMode, on Changelog.* Changed `autoModeEnabled` set to `false` through device management to take effect without a restart. At the app's next configuration check (every 10 minutes by default), running Cowork tasks and Code sessions, except WSL sessions, leave …cowork/changelogsee the edit
How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up autoMode, on Changelog.
Anthropic's release notes agreeAdded --settings <file> to claude remote-control, which applies a settings file to every session it starts; if the file changes, no new…
