imprnt-plugin-telegram
v0.1.0
Published
imprnt plugin: your vault from your phone - an imp lair session bridged to Telegram via Claude Code channels. Recall-first phone replies, one start command, no daemon.
Maintainers
Readme
imprnt-plugin-telegram
Your vault, reachable from your phone. A long-lived imp session runs in the lair with Claude Code's Telegram channel enabled. You text your bot from anywhere, the session searches the vault on your machine and texts the answer back. The vault never leaves the machine. Only the conversation does.
Built on Claude Code channels (research preview, v2.1.80+, claude.ai or Console auth, needs
Bun). This plugin wraps the official telegram@claude-plugins-official channel
with the vault-side behavior rules and a start command.
Install
imprnt plugin add telegramThat wires the behavior fragment (recall-first, phone-sized replies, never paste a whole note). Then the one-time channel setup, in any Claude Code session:
- Create a bot: open BotFather in Telegram, send
/newbot, copy the token. - Install the official channel plugin:
/plugin install telegram@claude-plugins-official(if it is not found, run/plugin marketplace add anthropics/claude-plugins-officialfirst), then/reload-plugins. - Give it the token:
/telegram:configure <token>(or exportTELEGRAM_BOT_TOKENin your shell instead, per the imprnt secrets rule - either way it never lands in the project). - Start the link (below), text the bot anything, and pair:
/telegram:access pair <code>, then/telegram:access policy allowlistso only you can reach the session.
Use
sh plugins/telegram/link.shThis runs imp lair --channels plugin:telegram@claude-plugins-official under caffeinate -i
(macOS), so the Mac stays awake while the link is up. Stop with Ctrl-C. It is a command you run
when you leave the desk, never a daemon: nothing starts by being installed.
Then text the bot from your phone: "what do I know about the access-platform cutover?", "remember: the dentist moved to the 24th". The session recalls, answers, files.
Honest constraints
- The session answers only while it is running on an awake machine. A message sent while the link is down arrives when you next start it (Telegram holds undelivered bot updates for a while), and there is no way to cold-start a local session from the phone.
- Telegram bot chats are not end-to-end encrypted. The vault stays home, but your questions and the answers transit Telegram's servers. Keep the bot private and the allowlist on.
- A permission prompt pauses the session until approved. Run the lair with your usual allow rules so recall/read paths do not prompt, or approve from the terminal when you are back.
- Channels are a research preview: the
--channelssyntax may change, and only Anthropic-allowlisted channel plugins can register, which is why this plugin wraps the official one instead of shipping its own.
Remove
imprnt plugin rm telegramAdd --purge to delete plugins/telegram/. To remove the channel itself:
/plugin uninstall telegram@claude-plugins-official, and delete
~/.claude/channels/telegram/.env if you configured the token there.
