Unclear The finding shows --disallowed-tools taken off the rejected list but not whether cloud sessions now apply it.
What
Cloud sessions are Claude Code sessions that run on Anthropic's servers instead of your computer. When you pass --tools to one, it is refused with a message that fits the situation:
- When attaching to an existing cloud session, it explains that the session keeps the tool list it was created with
- Otherwise, it suggests using
--disallowed-toolsto keep particular tools out
--disallowed-tools has also been removed from the list of flags that cloud sessions refuse.
Why
The message now says what to do instead of just refusing the flag. To keep certain tools out of a cloud session, use --disallowed-tools.
Names in the bundle--tools--disallowed-tools
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 since
Anthropic's documentation has since written up --disallowed-tools, on Error reference.
* Fix the rule at its source, which the full warning names in parentheses: a settings file path, or the flag itself for `--allowed-tools` and `--disallowed-tools`. A `claude-settings-<hash>.json` path that doesn't exist on disk stands for …errors see the edit
Confirmed since
Anthropic's documentation has since written up --tools, on Claude Code changelog.
* Fixed continued or resumed conversations losing earlier extended thinking when relaunched with a `--tools` list that leaves out a built-in tool offered earlier in the conversationchangelog see the edit
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The finding shows `--disallowed-tools` taken off the rejected list but not whether cloud sessions now apply it.
Anthropic's documentation agrees
Anthropic's documentation has since written up --tools, on Claude Code changelog.