{"version":"2.1.281","anchor":"disallowedtools-now-forwarded-to-cloud-sessions","canonical_anchor":"disallowedtools-now-forwarded-to-cloud-sessions","heading":"--disallowedTools now forwarded to cloud sessions","tier":"use","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/disallowedtools-now-forwarded-to-cloud-sessions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### --disallowedTools now forwarded to cloud sessions\n\nTools you block with --disallowedTools now stay blocked in cloud sessions you start\n\n**What**\n\n`--disallowedTools` is the command-line flag for denying Claude certain tools or certain uses of a tool. When you start a cloud session (a Claude Code session that runs on a remote machine), those deny rules are now passed along to it. This applies both to the existing way of starting cloud sessions without the interactive screen and to the new stripped-down one.\n\nThe `tengu_remote_create_session` event now also records how many tools were disallowed, as `disallowed_tools_count`.\n\n**Why**\n\nRestrictions you set on the command line now carry over to the cloud session, so a tool you meant to block locally is not available there by accident.\n\n- Area: Cloud Sessions\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}