You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Cloud SessionsArea: what it touches
ImprovementsKind: in v2.1.290,
ImprovementsSection of the release
Unclear The command's name is not known, and it is hidden from listings.
What
A hidden command, one not listed in help, reviews how Claude Code settings files differ before a cloud session uses them. It has changed in these ways:
Its description now says it reviews ~/.claude/settings.json, your user settings file, as well as the folder's .claude/settings.json and .claude/settings.local.json.
Its prompts say "settings file" instead of "project settings file" when your user settings file is among those being reviewed.
Its introduction now says "A cloud session runs commands here" where it used to say the session can write to this folder.
Why
The review you are asked to approve before trusting a cloud session now covers your user-level settings, not only the folder's.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe command's name is not known, and it is hidden from listings.
Anthropic's release notes agreeFixed sandboxed Bash commands on Linux running ConfigChange hooks and reloading settings mid-command when .claude/settings.json or…
