Telegram plugin: notifications/claude/channel not injected into conversation (Claude Code 2.1.80)

Resolved 💬 3 comments Opened Mar 20, 2026 by enzobf-7 Closed Mar 24, 2026

Bug Report

Plugin: telegram@claude-plugins-official (v0.0.1)
Claude Code version: 2.1.80
Platform: macOS Darwin 25.3.0

Description

The Telegram MCP plugin receives messages correctly (bot polls Telegram, gate passes the message, typing indicator is sent via sendChatAction), but the notifications/claude/channel MCP notification is never injected into the Claude Code conversation.

Steps to reproduce

  1. Install the Telegram plugin (claude plugins install telegram@claude-plugins-official)
  2. Configure a bot token and pair a user
  3. Send a DM to the bot from an allowlisted user
  4. The bot shows a typing indicator on Telegram ✅
  5. No message appears in the Claude Code conversation ❌

Diagnosis

  • The bun MCP server process starts and logs polling as @<botname>
  • Telegram updates are consumed by the polling loop (confirmed via getUpdates API)
  • Typing indicator (sendChatAction) is sent successfully
  • mcp.notification({ method: 'notifications/claude/channel', params: {...} }) is called
  • The notification never appears as a <channel source="telegram"> message in the conversation

Workaround

Added a fallback that writes incoming messages to ~/.claude/channels/telegram/inbox-fallback.jsonl so they can be read manually.

Notes

This was reportedly working before (user confirms it worked previously). The issue appears to be in how Claude Code 2.1.80 handles notifications/claude/channel MCP notifications from plugin-spawned servers.

View original on GitHub ↗

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