{"version":"2.1.281","anchor":"remote-session-create-forwards-disallowedtools","canonical_anchor":"remote-session-create-forwards-disallowedtools","heading":"Remote session create forwards disallowedTools","tier":"notice","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/remote-session-create-forwards-disallowedtools","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Remote session create forwards disallowedTools\n\nCreating a remote session now sends the caller's disallowedTools, combined with the built-in list for device-bound sessions\n\n**What**\n\nWhen Claude Code creates a remote session, the request now includes `disallowed_tools`. These are tools the session is not allowed to use. The list combines the caller's own `disallowedTools` with the built-in list used for device-bound sessions. The request carries `disallowedTools` alongside `allowedTools`.\n\nBefore, the request sent only the fixed built-in list, and only for device-bound sessions.\n\n**Why**\n\nTools you block when starting a remote session are now actually passed on to that session, instead of being dropped.\n\n- Area: Cloud Sessions\n- Names: `disallowedTools`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}