PATAPIM × Telegram

Talk to your terminal from Telegram. No setup.

PATAPIM pings you when Claude finishes. You reply from your phone. Your reply lands in the terminal, like you typed it yourself.

🦆
@botpatapimbot
PATAPIM remote control
✅ Migration complete. 12 files changed, all tests pass.
Want me to push? from terminal · main
yes, and open the PR
Pushed main. PR opened: #842 — "feat: bidirectional telegram" 2 sec ago

What it does

🔔

Get pinged when Claude needs you

"Need approval to delete this." "Build done." "Tests failing — what now?" Claude reaches you on Telegram, you don't have to babysit the terminal.

↩️

Reply from your phone, in real terminal

Type a reply in Telegram. It arrives in the active PATAPIM terminal as if you'd typed it. No copy-paste, no menus. Just text.

📦

Goes both ways. Resilient.

If your laptop is closed, messages queue up. When PATAPIM comes back online, they flow through. Up to 7 days of buffer.

Three terminals open. One chat. How?

Most of us juggle more than one terminal. Here's how PATAPIM keeps it sane on the phone.

💬

All your terminals share one chat

No separate chat per terminal. Everything lands in the same conversation — but every message is tagged with which terminal it came from, so you always know what you're looking at.

✅ build green terminal · patapim/main
❌ tests failing on auth.test.js terminal · website/feature-auth
⏳ migration running, ~3 min left terminal · backend/migrate-2026
↪️

Two ways to reply, two routings

Reply to a specific message (long-press → Reply in Telegram) → your text goes to the terminal that sent that message, no matter which one is in focus on your laptop.

Just send a message (no reply) → it goes to the terminal you're currently focused on in PATAPIM. So if you're staring at tab 3 and type from your phone, tab 3 gets it.

The bot also tells you when there's no terminal to route to (e.g. you closed PATAPIM or replied to a message from a session that's gone).

⌨️

Slash commands? Yes. Shell commands? Also yes.

Whatever you type lands in the terminal exactly as if you'd typed it on your keyboard, then pressed Enter. There's no special parsing.

  • /clear — clears Claude context
  • /compact — Claude summary
  • /model opus — switch model
  • git status — runs in your shell
  • y or yes — answers a Y/N prompt

It's literally remote-typing. If your keyboard would do it, Telegram will too.

Setup — 30 seconds

Open PATAPIM Preferences

⚙️ Preferences → Notifications → Telegram

Click "Connect to Telegram"

You'll get a 6-letter code like K7P3MX.

Open the bot, paste the code

@botpatapimbot opens. Press Start, send the code. That's it — your phone is now wired to your dev machine.

What changed

Telegram bots used to mean "create a bot, copy the token, find your chat ID, paste it all in." That's a project, not a feature. The new flow is one click.

Old way
  1. Talk to BotFather
  2. Create a bot
  3. Copy the token
  4. Find your chat_id
  5. Paste both in PATAPIM
  6. Hope it works
New way
  1. Click "Connect"
  2. Paste a 6-letter code

No tokens. No bots to manage. Nothing on your machine.

Quick answers

Is my code/data going through your servers?
Only the Telegram messages — same as if you used any Telegram bot. PATAPIM's relay is just a thin bridge so you don't have to manage a bot yourself. Your terminal output stays on your machine until you send a reply.
What if I want my own bot instead?
Still supported. In the same panel, switch to "Custom bot" and paste your token + chat_id like before. Default is the PATAPIM bot because life's too short.
Multiple machines?
Each PATAPIM install pairs with one chat. You can pair the same chat with a different install by re-running the connect flow. The new pairing replaces the old.
Voice messages? Photos?
Coming. Right now text only. Voice and image are next on the list.

Update PATAPIM and try it

Open Preferences → Notifications → Telegram. The button is right there.

Get the latest PATAPIM already installed? · just update