pi-telegram
https://github.com/badlogic/pi-telegram- Category
- Developer Tools
- Rank
- No. 3723Tools index
Previous survey · No. 3506 ·
- Pricing
- Open Source
- Type
- TOOL
- Use case
- Agent Building · Workflow Automation
- Interfaces
- Agent Skill / Plugin
- Builder
- badlogic
- GitHub
- 315 stars
- Date
About
Telegram DM bridge extension for pi — route Telegram conversations into your pi agent setup.
What it does
It lets one Telegram user converse with a running pi session through a bot. Text enters pi with a Telegram marker, while images and files download locally for agent access. Replies stream back during generation, and requested artifacts can return as attachments.
Why it's ranked here
The extension covers a surprisingly complete remote-agent loop: pairing, queued follow-ups, cancellation, media intake, streamed previews, long-reply splitting, and outbound files. Its narrow single-user, single-session model keeps the setup understandable, but also defines a firm ceiling.
What's good
The first DM user becomes the only accepted user, reducing accidental access after pairing. Messages arriving during a run wait in order, while stop commands abort active work. Draft streaming falls back to editable messages, and oversized replies are split for Telegram.
Tradeoffs
The bridge is session-local, and only one pi session should connect to a bot. It supports one allowed Telegram user, sends ordinary messages instead of quote-replies, and requires an explicit attachment tool when the agent needs to return files.
How to use it well
Use it when one person wants remote access to a specific pi session from Telegram, including image analysis and artifact exchange. Connect the bot only in its owning session. It does not cover shared team chats, multiple authorized users, or threaded reply workflows.
Technical notes+
package.json declares an ESM pi extension with index.ts as its entry point and peer dependencies on the pi AI, agent core, coding agent, and TypeBox packages. index.ts implements configuration persistence, Telegram Bot API requests, multipart uploads, local attachment downloads, filename sanitization, media typing, reply chunking, polling state, turn queues, preview throttling, and single-user pairing. README.md documents git installation, one-run loading, setup and connection commands, attachment behavior, cancellation, streaming fallback, and the MIT license.
Observed
- License
- MIT
- Primary language
- TypeScript
- Packaging
- ES module pi extension declared through package.json
- Install surface
- Install from the Git repository or load for a single pi run
- Interface
- pi slash commands, Telegram direct messages, and an outbound attachment tool
- Platform support
- Telegram Bot API connected to a local pi agent session
- Access model
- The first direct-message user is stored as the sole allowed Telegram user
Read from README.md, package.json, index.ts.
What it can do
Route Telegram messages to pi agent
Telegram direct messages → Messages forwarded to pi agent system
Bridge Telegram conversations with pi agent
Telegram chat conversations → Integrated conversation flow between Telegram and pi
Enable Telegram interface for pi agent
Pi agent setup and Telegram account → Telegram-accessible pi agent functionality
Forward pi agent responses to Telegram
Pi agent generated responses → Telegram messages sent to user
Establish bidirectional communication channel
Telegram DMs and pi agent system → Two-way message flow between platforms
Tags
Tech Stack
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.