Telegram plugin: inbound notifications stop working after new session

Resolved 💬 2 comments Opened Mar 30, 2026 by vladimirbrasil Closed May 3, 2026
  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

Bug

Telegram plugin stops delivering inbound notifications/claude/channel after opening a new terminal/session. Works on first install only.

Steps to reproduce

  1. Install telegram plugin, pair, send messages — works
  2. Close terminal, open new session
  3. Send message via Telegram — never arrives in Claude Code

Diagnosis

  • Bot token valid (getMe OK)
  • Polling active (TCP ESTAB to 149.154.166.110:443)
  • getUpdates via curl returns messages correctly
  • Running server.ts manually with open stdin: notifications emitted correctly on stdout as JSON-RPC
  • MCP tool calls (reply, react) work fine — only inbound direction is broken
  • Tested with both bypassPermissions and allowEdits modes — same result

Environment

  • Claude Code v2.1.87
  • Plugin: telegram@claude-plugins-official v0.0.4
  • OS: Ubuntu Linux 5.15.0-171-generic
  • Runtime: Bun

View original on GitHub ↗

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