Answer: Admins on Team and Enterprise plans can restrict which channel plugins can run by setting `allowedChannelPlugins` in managed settings, which replaces the default Anthropic-maintained allowlist. This setting requires `channelsEnabled: true`. Status: Confirmed Entry: tool/claude-code/permissions-and-security/restrict-channel-plugins Revision: 2 Digest: sha256:cdd12866dab8de57 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:03:23Z Last changed: 2026-11-19T12:14:07Z (block entirely: channelsEnabled → —) Last verified: 2026-11-20T12:18:25Z Next check: 2026-11-21T12:18:25Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of setting name | allowedChannelPlugins | [1] | 2026-11-20 required setting | channelsEnabled: true | [1] | 2026-11-20 plans | Team and Enterprise | [1] | 2026-11-20 empty array effect | you block all channel plugins from the allowlist | [1] | 2026-11-20 bypass flag | --dangerously-load-development-channels | [1] | 2026-11-20 Sources: [1] Anthropic. "Push events into a running session with channels". https://code.claude.com/docs/en/channels.md Role: primary. Accessed: 2026-11-20T12:18:25Z Quote: "replace that allowlist with their own by setting `allowedChannelPlugins` in managed settings" (Supports: setting name) Quote: "This setting requires `channelsEnabled: true`." (Supports: required setting) Quote: "Admins on Team and Enterprise plans can replace that allowlist with their own" (Supports: plans) Quote: "If you set an empty array, you block all channel plugins from the allowlist" (Supports: empty array effect) Quote: "`--dangerously-load-development-channels` can still bypass that block for local testing" (Supports: bypass flag) Published: 2026-11-20T03:07:15Z Snapshot SHA-256: 5869e37fca1da097cb678b0c7471048479643367a6ed04c854dd4e72ec80301e (captured 2026-11-20T12:18:24Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. Cross-check: not-available at 2026-11-20T12:18:25Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:18:25Z Last attempt: 2026-11-20T12:18:25Z Notes and limitations: Extracted automatically from a single official source (section "Restrict which channel plugins can run"). Related: https://latestn.com/tool/claude-code/permissions-and-security/restrict-network-egress How do I restrict network egress for Claude Code in a dev container? https://latestn.com/tool/claude-code/permissions-and-security/review-plugin-before-install How do I review a Claude Code plugin before installing it? https://latestn.com/tool/claude-code/permissions-and-security/run-without-permission-prompts How do I run Claude Code in a dev container without permission prompts? https://latestn.com/tool/claude-code/permissions-and-security/report-security-issue How do I report a security issue in Claude Code? https://latestn.com/tool/claude-code/permissions-and-security/report-security-vulnerability How do I report a security vulnerability in Claude Code? https://latestn.com/tool/claude-code/permissions-and-security/require-approval-cross-machine-messages How do I require approval for cross-machine messages in Claude Code? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-19T12:14:07Z | changed | block entirely: channelsEnabled → — | [1] 2026-11-19T12:14:07Z | changed | empty array effect: empty array → you block all channel plugins from the allowlist | [1] 2026-11-13T03:03:23Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/claude-code/permissions-and-security/restrict-channel-plugins/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/claude-code/permissions-and-security/restrict-channel-plugins POST: https://latestn.com/dispute/tool/claude-code/permissions-and-security/restrict-channel-plugins with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/claude-code/permissions-and-security/restrict-channel-plugins?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I restrict which channel plugins can run in Claude Code? Revision 2, last verified 2026-11-20T12:18:25Z. https://latestn.com/tool/claude-code/permissions-and-security/restrict-channel-plugins (accessed 2026-11-21T09:57:32Z). @misc{LatestN_tool_claude_code_permissions_and_security_restrict_channel_plugins_r2, title = {How do I restrict which channel plugins can run in Claude Code?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/claude-code/permissions-and-security/restrict-channel-plugins}}, note = {Revision 2; digest sha256:cdd12866dab8de57; last verified 2026-11-20T12:18:25Z; accessed 2026-11-21T09:57:32Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/claude-code/permissions-and-security/restrict-channel-plugins