$ cat ~/map/pi-telegram.md
Pi Telegram
Telegram frontend pairing one bot with one live pi session — owner-only input, steering, and Rich Message answers.
tools✓ Sep 10
Facts
- repository
- github.com/mbundgaard/PiTelegram ↗
- GitHub Stars
- ★ 0
- Forks
- 0
- license
- MIT
- npm / mo
- —
- last push
- Sep 27, 2026
install
pi install npm:@comput/pi-telegram## TL;DR
A Telegram frontend for live pi coding-agent sessions: one project bot paired to one session, with owner-only input, !-prefixed steering, follow-up requests, private reasoning, and native Rich Message answers.
## Key points
- $Pairs one project-specific bot with one live pi session; after getMe token validation, manually created bots pair through a one-time code; sending the code to the bot establishes the authorized owner.
- $Input grammar: a normal message starts a separate follow-up request, !message steers active work, !!message sends a literal leading !, and stop or /stop cancels the current Telegram task.
- $Telegram first shows a native Rich Thinking or tool-activity draft, replaced by one evolving plain progress line on the first public commentary; hidden reasoning and raw tool traffic never leave the machine.
- $Manager mode lets a manager bot that reports can_manage_bots create project bots through an approval link with an explicitly chosen username; manual mode uses a bot you create yourself. The mode decision and the global manager configuration live in ~/.pi/agent/pi-telegram/settings.json.
- $Per-project bot credentials are stored in .pi/pi-telegram.local.json and added to the local Git exclude automatically; tokens are never accepted through model tool arguments or chat.
- $The telegram_send_file tool uploads project files as native Telegram documents, restricted to the active project's canonical paths and blocking credential, private-key, environment, and .git files, subject to Telegram's 50 MB upload limit with optional captions up to 1,024 characters.
- $Setup and status run as pi slash commands: /telegram-setup, /telegram-setup-manager, /telegram-setup-bot, and /telegram-status; completed responses persist as native Telegram Rich Messages.
## FAQ
Q How is Pi Telegram different from a plain Telegram bridge?
It is pi-native: setup, pairing, and status run as pi slash commands, the connection is stored per project in .pi/pi-telegram.local.json, and completed answers persist as native Telegram Rich Messages rather than plain text bubbles.
Q Who can talk to the bot?
Only the paired owner — Pi Telegram accepts only private text from the owner established by the pairing code, and never sends hidden reasoning or raw tool results to Telegram.
## References
## Related entries
$ Pi Telegram Gateway
Telegram gateway on the official pi SDK — per-chat sessions, follow-up queueing, mid-flight steering, and cron jobs.
$ aft
Sensorimotor-cortex layer that ships thin adapters for Pi and OpenCode, replacing raw read/write/edit/bash with semantic operations.
$ CCompactor
Turns finished coding-agent sessions — Pi, Claude Code, Codex — into compact, verified, provenance-linked handoff artifacts, in TypeScript.
## Guides
Last updated: Sep 10, 2026