{"version":"2.1.296","anchor":"cloud-tools-restriction-handling-reworked","canonical_anchor":"cloud-tools-restriction-handling-reworked","heading":"Cloud sessions now refuse --tools restrictions they cannot apply instead of dropping them","tier":"use","area":"Cloud Sessions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/cloud-tools-restriction-handling-reworked","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Cloud sessions now refuse --tools restrictions they cannot apply instead of dropping them\n\nStarting a cloud session with --tools now checks the list and gives a clear error for lists, environments or existing sessions it cannot honour\n\n**Unclear.** Which `--tools` lists are now accepted for cloud sessions is not stated.\n\n**What**\n\n`--tools` is the command-line flag that limits which built-in tools Claude can use. For cloud sessions, which run on Anthropic's servers instead of your computer, Claude Code now checks this flag before the session starts.\n\n- The `--tools` list is sorted into the default set, refused lists and other lists. Some lists are now accepted.\n\n- Names that are malformed, presets, negations or rules are refused, as are an empty list and a list over a maximum length. The error says a cloud session cannot apply these tool restrictions, so they are refused rather than silently dropped. The same applies to `--disallowed-tools`.\n\n- A refused list gives a `tool_restriction` error naming the tools at fault.\n\n- Using `--tools` when attaching to an existing cloud session gives an `attach_restriction` error, saying a flag cannot change an existing cloud session.\n\n- On Remote Control, self-hosted or unknown environments, the session is not started, for example: \"The cloud session was not started: --tools is not supported in a Remote Control environment.\"\n\n- A separate error covers `--tools` when the device is bound without a deferred prompt.\n\n- The old check after creation, `builtin_tools_not_echoed`, is removed. Session creation now checks the built-in tools itself and stops if they cannot be applied.\n\n**Why**\n\nIf you pass tool restrictions to a cloud session, you now get a clear error when they cannot be honoured, instead of a session that may run without the limits you asked for.\n\n- Area: Cloud Sessions\n- Names: `--tools`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}