[BUG] Telegram plugin intermittently drops inbound messages on Windows

Resolved 💬 3 comments Opened Mar 24, 2026 by tommylee1115 Closed Mar 27, 2026

Description

The official Telegram channel plugin (v0.0.2) intermittently fails to deliver inbound messages to the active Claude Code session on Windows. Outbound messages (via the reply tool) work consistently, but inbound messages are silently dropped with no error or feedback to the Telegram sender.

Environment

  • OS: Windows 11 Home 10.0.26200
  • Claude Code: latest (as of 2026-03-24)
  • Telegram plugin: v0.0.2 (claude-plugins-official)
  • Shell: Git Bash

Steps to Reproduce

  1. Install the Telegram plugin via claude-plugins-official
  2. Configure access and approve a user
  3. Send messages from Telegram to the bot
  4. Observe that some messages are received and responded to, while others are silently dropped

Observed Behavior

  • Messages sent in rapid succession are more likely to be dropped
  • Longer messages occasionally fail to be delivered to the session
  • No error is shown on either the Telegram or Claude Code side — the sender has no way to know if the message was received
  • Only one Claude Code process running (ruled out zombie process contention)
  • Configuration verified correct (user ID in allowlist, plugin enabled)

Expected Behavior

All inbound Telegram messages should be reliably delivered to the active Claude Code session, or at minimum, a delivery failure should be surfaced.

Related Issues

  • #36431 - Inbound MCP channel notifications not delivered
  • #36477 - Channels mode stops processing after first response
  • #36964 - Telegram channel MCP server dies on Windows
  • #36802 - Notifications not delivered to session

Additional Context

This makes it difficult to rely on the Telegram channel for async communication with Claude Code, especially when away from the laptop. A notification retry mechanism or at least a delivery acknowledgment would significantly improve reliability.

View original on GitHub ↗

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