Telegram & your phone

The same council, the same vault, the same commands — from your phone. Prevail’s Telegram bridge runs the cockpit headless and talks to you through a bot.

Setup

Create a bot. Message @BotFather on Telegram, send /newbot, and copy the token it gives you.
Register the token:
Terminal window
```
prevail telegram setup <bot-token>
```
It’s stored at ~/.prevail/telegram.json with chmod 0600.
Allowlist yourself. This is mandatory — the bridge ignores anyone not on the list:
Terminal window
```
prevail telegram add-user <chat-id>
```
(Your chat ID comes back the first time you message the bot, or from a bot like @userinfobot.)
Run the daemon:
Terminal window
```
prevail daemon --telegram
```
It polls Telegram for your messages and ticks any scheduled briefings.

Using it

Once the daemon is running, message your bot like you’d type in the cockpit:

/council should I take the contract or stay salaried?
/domain wealth
/framework bluf
what's my runway if I quit today?

The council convenes on your machine, the verdict comes back as a message, and the turn is logged into your vault exactly as if you’d asked from the terminal.

Defaults for the bridge

Set what mobile turns default to, so you don’t have to specify every time:

prevail telegram set-default cli claude
prevail telegram set-default domain chief
prevail telegram set-default council on

Managing access

prevail telegram status              show config + allowlisted users
prevail telegram add-user <id>       grant access
prevail telegram remove-user <id>    revoke access

You can also manage all of this from inside the cockpit with /telegram (alias /tg).

Where to run it

Run prevail daemon --telegram on the always-on machine that holds your vault — a Mac mini, a home server, a cheap VPS with your CLIs logged in. It needs the vault and the AI CLIs; it doesn’t need your laptop to be awake. The daemon also writes a PID file so a second copy won’t start by accident.