[BUG] --channels ignored after v2.1.195 update (plugin:telegram@claude-plugins-official)

Open 💬 4 comments Opened Jun 28, 2026 by junwookimdiw

Environment

  • Claude Code version: 2.1.195
  • OS: Ubuntu 24.x (junwoo-kim-700A4K)
  • Plan: Pro (personal, no org)
  • Plugin: telegram@claude-plugins-official v0.0.6

Summary

--channels plugin:telegram@claude-plugins-official was working correctly until June 25, 2026. After the v2.1.195 update (released June 26), the flag is silently ignored at startup:

--channels ignored (plugin:telegram@claude-plugins-official)

Steps to Reproduce

claude --channels plugin:telegram@claude-plugins-official

Expected Behavior

Telegram channel plugin registers and starts polling for messages.

Actual Behavior

Plugin is ignored at startup with the message:

--channels ignored (plugin:telegram@claude-plugins-official)

Configuration

~/.claude/settings.json has:

{
  "enabledPlugins": {
    "telegram@claude-plugins-official": true
  }
}

No CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC set. No org/team plan — pure Pro personal account.

Suspected Cause

The v2.1.195 changelog mentions:

Fixed external plugins enabled only via project .claude/settings.json not requiring explicit install consent on every loader path.

This change appears to have introduced a regression in the channels plugin loader path, causing --channels to be ignored even for properly installed and configured plugins on personal Pro plans.

Workaround

claude --channels plugin:telegram@claude-plugins-official \
       --dangerously-load-development-channels plugin:telegram@claude-plugins-official

This works but should not be required for an installed, allowlisted channel plugin on a personal Pro account.

Additional Context

  • Plugin is properly installed (v0.0.6 in ~/.claude/plugins/cache/)
  • Marketplace (claude-plugins-official) last updated 2026-06-28
  • Bun is installed and functional
  • The same setup worked without issues before v2.1.195

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗