{"version":"2.1.285","anchor":"cloud-sessions-tools-handling-and-error-messages","canonical_anchor":"cloud-sessions-tools-handling-and-error-messages","heading":"Cloud sessions gain messages for limiting tools with --tools","tier":"notice","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/cloud-sessions-tools-handling-and-error-messages","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Cloud sessions gain messages for limiting tools with --tools\n\nCloud sessions now have messages for limiting a session to the tools you list with `--tools`, covering empty lists, unsupported cases and org limits\n\n**Unclear.** It is not clear whether limiting cloud sessions with --tools can be used yet.\n\n**What**\n\nClaude Code now has messages for limiting a cloud session to the tools you list with `--tools`. A cloud session is a Claude Code session that runs on Anthropic's servers. The messages cover these cases:\n\n- An empty `--tools` list is refused\n\n- `--tools` together with a prompt is refused for sessions attached to this computer\n\n- Your organization does not offer this limit\n\n- A duplicate session was merged into another\n\n- The tool list could not be confirmed, in which case the session is archived\n\nA separate new message warns when a `--disallowed-tools` rule has an opening parenthesis that is never closed, because a cloud session would drop that rule.\n\n**Why**\n\nThis points to cloud sessions gaining the ability to be restricted to certain built-in tools, rather than refusing `--tools` outright. Check `--disallowed-tools` rules for unbalanced parentheses, since a broken rule would be dropped instead of applied.\n\n- Area: Cloud Sessions\n- Names: `--tools`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}