Telegram channel plugin: notifications/claude/channel accepted but never surfaced in conversation

Resolved 💬 3 comments Opened Apr 7, 2026 by scaleitsimply Closed Apr 11, 2026

Description

Telegram channel plugin (0.0.4) delivers notifications/claude/channel notifications — Claude Code accepts them without error, but the messages never appear in the conversation.

Environment

  • Claude Code: 2.1.92 (latest as of 2026-04-07)
  • Telegram plugin: 0.0.4
  • OS: Ubuntu 24.04 (VPS)
  • Node.js: v20

What works

  • Plugin loads, MCP tools are available (reply, react, edit_message, download_attachment)
  • Outbound messages work — reply tool sends messages successfully
  • Bot receives incoming messages (confirmed via debug logging)
  • MCP notification fires and reports "DELIVERED OK"

What doesn't work

  • Inbound messages never appear in the conversation as <channel> blocks
  • No error is returned — the notification is silently dropped

Debugging done

  • Confirmed via /tmp/telegram-debug.log that mcp.notification({ method: 'notifications/claude/channel', ... }) fires and resolves without error
  • Ruled out: competing pollers (no other Claude process polling), 409 Conflict (getUpdates returns clean), webhook interference (getWebhookInfo shows none set), plugin crash, missing dependencies, wrong bot (confirmed via getMe)

Expected behavior

Inbound Telegram messages should be injected into the conversation context as <channel> blocks when the plugin sends a notifications/claude/channel notification.

Actual behavior

Notification is accepted by Claude Code (no error thrown), but silently dropped — never surfaces in the conversation.

View original on GitHub ↗

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