notifications/claude/channel MCP notifications received by Claude Code CLI but never displayed (telegram plugin)

Resolved 💬 2 comments Opened Apr 3, 2026 by dariuskavb Closed May 5, 2026

Environment

  • Claude Code version: 2.1.91
  • OS: macOS (darwin, aarch64)
  • Plugin: telegram@claude-plugins-official v0.0.1
  • Bot: @PxCC1_bot (Telegram)

Behavior

Inbound Telegram messages are never displayed in the Claude Code CLI session, even when the session is idle at the prompt.

What works

  • Outbound direction works fine: reply tool sends messages to Telegram successfully
  • Bot polls Telegram successfully: getUpdates always returns empty after messages are sent
  • Bot correctly authenticates and passes the access gate (allowlist policy, correct user ID)

Root cause investigation

  1. Confirmed bot process is the correct child of the Claude Code process (PID chain verified)
  2. Confirmed MCP stdio socket is open and connected between bot and Claude Code — bot stdout FD peer matches Claude Code's open socket FD (verified via lsof)
  3. Bot calls mcp.notification({ method: 'notifications/claude/channel', params: { content, meta } })
  4. Claude Code receives the notification on the connected socket
  5. Claude Code does not display the message — in any session state (idle or active)

Steps to reproduce

  1. Install telegram@claude-plugins-official plugin
  2. Configure bot token and allowlist a Telegram user
  3. Send a message from Telegram to the bot
  4. Observe: getUpdates returns empty (bot consumed the update)
  5. Observe: no channel message appears in Claude Code CLI session

Expected behavior

Inbound Telegram message should appear as:

<channel source="telegram" chat_id="..." message_id="..." user="..." ts="...">message text</channel>

Notes

  • tengu_harbor: True in cachedGrowthBookFeatures
  • telegram is listed in tengu_harbor_ledger
  • Feature appears enabled but not functional in CLI
  • Tested in both idle and active conversation states
  • Tested with a single bot instance (no 409 conflicts)

View original on GitHub ↗

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