Pidge vs a Telegram bot

A Telegram bot is the most common way developers wire an agent to their phone. It is free. It is two-way-ish: your agent sends a message, you type back. You may already have one running. We respect that, and this page concedes it up front.

Here is the honest line. If you want free, you already live in Telegram, and you don't need OS-level urgency or a guaranteed answer path back to the agent, a Telegram bot is a reasonable choice. Keep it. The rest of this page is for the cases where it stops being enough.

A bot lives inside a chat app. Pidge lives in the OS.

A Telegram message is a Telegram message. It can't ring through silent mode. It can't hold a countdown on your lock screen. It can't ask for Face ID before a sensitive action. The chat app is the ceiling.

Pidge delivers at the level of the operating system, and you set the rules. Five profiles, owned by you:

• message — quiet; respects silent mode and Focus.
• important — the recommended default: a time-sensitive banner, no alarm.
• urgent — if you don't answer in time, it becomes a real AlarmKit alarm that rings through silent mode and Focus.
• event — a countdown Live Activity to a known moment.
• live — a progress card on the lock screen, updated in place.

The agent requests a level. Your per-channel ceiling decides what it actually gets. An over-ceiling send is delivered at the channel's ceiling instead, and the agent is told why. Nothing is silently dropped. A bot has none of this: every message lands the same way.

A messenger built for agents, not a bot squeezed into one.

In Telegram, your agent is a bot in a list of chats with humans. In Pidge, every agent gets its own channel — a contact with a face, a color, presence, and its own delivery rules — and every channel is a real thread. Reports, questions and approvals come in; your replies, voice notes and photos go out.

It works like any messenger: what you send waits in the agent's queue until it's on the line. Unlike any messenger, you can see exactly what happened to it. "listening now" lights up when an agent is connected, and the ✓✓ turn green only once it actually handled what you said — not when the server received it. Every session signs with a stable name, so you always know which one is talking. That is a different thing from a chat bubble.

The answer gets back to the agent. Guaranteed, not glued.

With a bot, "two-way" means you type into a chat and your glue code polls for it — and hopes. With Pidge, the round trip is the product: the agent blocks on ask, you tap an answer on the lock screen, and your choice returns as JSON on the agent's stdout. Both sides see the state — delivered, seen, answered — and a message stays leased until the agent acks it, so a crash re-serves it instead of losing it.

One paste, not BotFather plus glue code.

Setting up a Telegram bot means talking to BotFather, copying a token, finding your chat id, and writing the glue that maps your agent's output to the bot API. It works. It is also plumbing you maintain.

Pidge is one paste. The agent reads a self-documenting manifest (GET /api/v1/manifest) and onboards itself — four real agents did this with zero docs. The CLI is pidge-cli on npm, Node 18+, nothing to install; the round trip is about a second over WebSocket, with an HTTP long-poll fallback.

The feed is typed deliverables, not chat scroll.

In a bot, everything is a chat bubble. The finished report, the "still working" ping and yesterday's noise look the same and scroll away together. Pidge sends are typed — the same five names as the profiles — so the feed is a list of deliverables. Reports render as real Markdown with tables and task lists. Images show on the banner and in the feed. Real files open in Quick Look and save to Files. And you can reply to any of it, even last week's.

Privacy, plainly — with an optional seal.

A bot lives in a cloud chat: Telegram bot conversations are not end-to-end encrypted, and your agent's traffic sits on Telegram's servers alongside your group chats.

Pidge's default is simple: your messages are encrypted in transit; we don't read them, don't train models on them, don't sell data, and you can delete everything whenever you want. When a channel deserves more, make it a sealed channel — optional end-to-end encryption, per channel, on your 1:1 agent channels. Titles, bodies, replies, action labels, tap-to-copy values, deep links, filenames and the photo and file bytes themselves are sealed on your device, and the server stores only ciphertext for those fields. Live Activity status and delivery metadata are not sealed; the manifest lists exactly what is. Group channels are encrypted in transit, not end-to-end — shared spaces, like any team chat.

Side by side

When a Telegram bot is the better call

We mean this. Pick the bot when:

• You want free.
• You already live in Telegram all day.
• You only need a message to arrive — no alarms, no lock-screen progress, no Face ID.
• The traffic is low-stakes, so plaintext on Telegram's servers doesn't bother you.

Pidge earns its price when the agent's work matters enough that you want to control how loudly it reaches you, know your answer got back to the agent, and act on it in one tap — without leaving the lock screen.

See also: Pidge vs Pushover · Pidge vs ntfy · Pidge vs Bark