{"version":"2.1.285","anchor":"remote-session-creation-passes-disallowed-tools","canonical_anchor":"remote-session-creation-passes-disallowed-tools","heading":"Cloud sessions started with --environment prepare to pass on blocked tools","tier":"notice","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/remote-session-creation-passes-disallowed-tools","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Cloud sessions started with --environment prepare to pass on blocked tools\n\nCreating a cloud session with --environment can now send a list of blocked tools, though that list is always empty in this build\n\n**Unclear.** Because the list is always empty in this build, it is unclear whether any of this changes how a cloud session behaves yet.\n\n**What**\n\nThe `--environment` flag creates a new cloud session, meaning a Claude Code session running on a remote machine. When it is used without the interactive screen, the request that creates the session can now include a list of disallowed tools, which are tools the session is not allowed to use. Claude Code also records how many tools were on that list. If one of your deny rules (a permission rule that blocks a tool) is written without its closing bracket, creating the session now stops with an error.\n\nIn this build the list of disallowed tools is always empty.\n\n**Why**\n\nThis prepares for your deny rules to be carried over to cloud sessions, so a tool you block locally would also be blocked remotely.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}