Language: 日本語English

telegram Plugin

Category
Productivity
Topics
Project Management & Collaboration · Claude Code Customization & Workflow
First seen
2026-07-09
Last confirmed
2026-07-13
Explanation last updated
2026-07-12

The explanation below is AI-generated. Please verify it against the sources.

The telegram plugin connects a Telegram bot to Claude Code through an MCP server, forwarding bot messages to a Claude Code session. According to the README, setup requires Bun, creating a bot via BotFather, installing the plugin, configuring the bot token with /telegram:configure, relaunching Claude Code with the --channels plugin:telegram flag, and pairing via a code the bot sends. Access is then managed with /telegram:access, with policies such as pairing and allowlist documented in ACCESS.md. The assistant can reply, react using Telegram's fixed emoji whitelist, and edit its own previously sent messages, but the Telegram Bot API exposes no message history or search, so the bot only ever sees messages as they arrive.

Overview

This is a Claude Code plugin rather than a standalone SaaS: it runs a local MCP server (on Bun) that logs into Telegram as a bot, relays incoming user messages to a Claude Code session, and exposes reply, react, and edit_message tools to the assistant, with access controlled through pairing codes and allowlists stored in access.json.

What you can do with telegram

  • Create a Telegram bot with BotFather and connect it to Claude Code using /telegram:configure and the claude --channels plugin:telegram@claude-plugins-official launch flag
  • Pair your Telegram account with /telegram:access pair so direct messages reach the assistant
  • Lock down access afterward with /telegram:access policy allowlist to stop unpaired strangers from getting pairing-code replies
  • Have the assistant reply to chats, react using Telegram's fixed emoji whitelist, and edit its own previously sent messages (e.g. progress updates)
  • Send and receive attachments up to 50MB; inbound photos are saved to ~/.claude/channels/telegram/inbox/ for the assistant to read
  • Run multiple bot instances on one machine with separate tokens and allowlists by pointing TELEGRAM_STATE_DIR at different directories per instance

Sources

Original description (English)

Telegram messaging bridge with built-in access control. Manage pairing, allowlists, and policy via /telegram:access.

History of telegram

Back to list