Skip to content

Telegram plugin: inbound messages not forwarded to session #38445

Closed as duplicate

Description

@marckam

Description

The Telegram plugin (telegram@claude-plugins-official v0.0.4) receives inbound messages via polling but does not forward them into the Claude Code session.

Environment

  • Claude Code on macOS (Darwin 25.3.0, Apple Silicon)
  • bun v1.3.11
  • Plugin version: 0.0.4

Steps to Reproduce

  1. Install the Telegram plugin: /plugin install telegram@claude-plugins-official
  2. Configure bot token in ~/.claude/channels/telegram/.env
  3. Complete pairing (access.json shows user in allowFrom)
  4. /reload-plugins — MCP server connects successfully
  5. Send a message to the bot in Telegram

Expected Behavior

The message should appear in the Claude Code session as a <channel source="telegram" ...> notification.

Actual Behavior

  • The message is consumed by the bot's getUpdates polling (confirmed: getUpdates returns empty after sending)
  • No message or notification appears in the Claude Code session
  • Outbound replies via mcp__plugin_telegram_telegram__reply work correctly — the bot can send messages to the user

Additional Observations

  • getMe confirms bot token is valid and polling is active
  • getWebhookInfo shows no webhook conflict
  • MCP tools (reply, react, edit_message) are all available and functional
  • /reload-plugins consistently reports 0 skills despite valid user-invocable: true SKILL.md files in the plugin's skills/ directory (possibly a separate issue)
  • Process is running and stderr shows telegram channel: polling as @<botname> with no errors

Activity

  1. github-actions commented on Mar 24, 2026

    @github-actions

    Found 3 possible duplicate issues:

    1. Telegram plugin: inbound messages not delivered to session (outbound works) #38446
    2. Telegram channel plugin: notifications/claude/channel events never reach the session #38285
    3. Telegram channel plugin: inbound messages not delivered to session #38415

    This issue will be automatically closed as a duplicate in 3 days.

    • If your issue is a duplicate, please close it and 👍 the existing issue instead
    • To prevent auto-closure, add a comment or 👎 this comment

    🤖 Generated with Claude Code

  2. github-actions commented on Mar 28, 2026

    @github-actions

    This issue has been automatically closed as a duplicate of #38446.

    If this is incorrect, please re-open this issue or create a new one.

    🤖 Generated with Claude Code

  3. github-actions commented on Apr 5, 2026

    @github-actions

    This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.

  4. locked as resolved and limited conversation to collaborators on Apr 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    duplicateThis issue or pull request already exists

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions