{"version":"2.1.281","anchor":"cloud-sessions-clearer-tools-rejection-disallowed-tool","canonical_anchor":"cloud-sessions-clearer-tools-rejection-disallowed-tool","heading":"Cloud sessions: clearer --tools rejection; --disallowed-tools no longer listed as rejected","tier":"notice","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/cloud-sessions-clearer-tools-rejection-disallowed-tool","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Cloud sessions: clearer --tools rejection; --disallowed-tools no longer listed as rejected\n\nCloud sessions reject `--tools` with a clearer message, and `--disallowed-tools` is no longer on the rejected list\n\n**Unclear.** The finding shows `--disallowed-tools` taken off the rejected list but not whether cloud sessions now apply it.\n\n**What**\n\nCloud 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:\n\n- When attaching to an existing cloud session, it explains that the session keeps the tool list it was created with\n\n- Otherwise, it suggests using `--disallowed-tools` to keep particular tools out\n\n`--disallowed-tools` has also been removed from the list of flags that cloud sessions refuse.\n\n**Why**\n\nThe message now says what to do instead of just refusing the flag. To keep certain tools out of a cloud session, use `--disallowed-tools`.\n\n- Area: Cloud Sessions\n- Names: `--tools`, `--disallowed-tools`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}