--channels flag inconsistently enables/disables between launches

Resolved 💬 3 comments Opened Mar 22, 2026 by drewjgray Closed Mar 26, 2026

Description

On v2.1.81, --channels plugin:telegram@claude-plugins-official inconsistently enables or disables channels between launches with no config changes.

Behavior

  • Sometimes shows: Listening for channel messages from: plugin:telegram@claude-plugins-official
  • Other times shows: --channels ignored (plugin:telegram@claude-plugins-official) / Channels are not currently available
  • No configuration changes between launches — same org settings, same plugin, same version

Additional Details

  • When "Listening" is shown, inbound MCP notifications (notifications/claude/channel) from the plugin server are not delivered to the conversation
  • Outbound tools (reply, react, edit_message) work correctly
  • Plugin server is confirmed working — bot receives Telegram messages, access gate passes, typing indicator fires, notification is sent via MCP
  • The server correctly declares experimental: { 'claude/channel': {} } capability

Environment

  • Claude Code v2.1.81
  • macOS (desktop app)
  • Team Enterprise Pro plan
  • Channels enabled in org admin config
  • Plugin: telegram@claude-plugins-official v0.0.1

View original on GitHub ↗

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