{"version":"2.1.81","anchor":"mcp-channel-permissions-gradual-rollout","canonical_anchor":"mcp-channel-permissions-gradual-rollout","heading":"MCP Channel Permissions [Gradual Rollout]","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.81\/e\/mcp-channel-permissions-gradual-rollout","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.81","markdown":"### MCP Channel Permissions [Gradual Rollout]\n\n**What**\n\nEnables MCP servers with the `claude\/channel` capability to push permission decisions and requests via notifications, allowing server-side permission management.\n\n**Status**\n\nFeature-flagged by `tengu_harbor_permissions` (default false). Additionally requires Teams\/Enterprise opt-in.\n\n**Details**\n\n- Uses `notifications\/claude\/channel\/permission` and `notifications\/claude\/channel\/permission_request` notification paths\n- MCP servers must declare both `claude\/channel` and `claude\/channel\/permission` in capabilities\n- Teams\/Enterprise opt-in: \"Teams\/Enterprise opt-in for channel notifications... Default off. Set true to allow; users then select servers via --channels.\"\n- Includes an FNV-1a hash-based identifier system with profanity filtering for generated codes\n\n**Evidence**\n\nChannel permissions infrastructure (gated by `tengu_harbor_permissions`, search for `\"notifications\/claude\/channel\/permission\"`)\n\n- Flag `tengu_harbor_permissions`: On for this account, and not off by default (read for one account on one subscription tier against v2.1.81; this account: on, anonymous baseline: on, compiled default: no gate table built for this version) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release."}