Messaging Channels
The problem this solves
The web app is a good place to work. It is a terrible place to be reached. The moment you leave your desk, an assistant you can only talk to in a browser tab stops being an assistant.
Messaging channels put AI Partner where you already are. Connect a channel and you can ask it something from your phone, get a briefing pushed to you before your first meeting, approve an action with one tap, and pick up in the web app later — in the same conversation, with the same memory.
Open it from System → Messaging.
The channels
The one to start with. Fast, reliable, and the channel used for one-tap approvals — approve, edit or skip an action from the notification itself.
Connected by scanning a QR code with WhatsApp → Linked Devices, the same way you link the desktop app. The code is short-lived — reconnect if it times out.
Talk to AI Partner in your workspace. Useful when the work is a team's work and the answer belongs where the team can see it.
A bot in your server. Good for a community or a personal always-on space.
For when the channel itself needs to be private.
Connecting a channel
Each channel's card in Messaging → Channels asks only for what that service needs, and tells you where in that service to find it — Telegram wants a bot token from BotFather, Slack wants its two app tokens, WhatsApp wants a QR scan.
- 1Fill in the channel's fields
Each field's hint names the exact screen in the other service to get it from.
- 2Connect
The card shows the channel's live connection state, so you can see it's actually up rather than merely saved.
- 3Send a test message
Give it a chat ID and some text and send. A message you receive on your phone is proof the whole path works — which is worth confirming before you start relying on it for approvals.
Connections survive a restart. Once a channel is connected it reconnects on its own — you don't re-pair it every time the app restarts.
The inbox
The Inbox tab shows messages arriving from every connected channel, in real time, in one place. It's the fastest way to confirm a newly connected channel is delivering, and a single view of what's coming in when several channels are live.
One partner, not five
This is the part that matters, and the part that's easy to get wrong: a message you send from Telegram reaches the same AI Partner as the web app.
- What you told it on your phone this morning is known in the browser this afternoon.
- Your documents, skills, integrations and connected computers are all available from a chat message.
- A goal you start from Telegram appears in the web app's goal panel, and you can watch it there.
- Facts it learns about you over a messaging channel go into the same memory the web app uses.
There is no separate mobile assistant with its own amnesia. There's one partner and several doors into it.
What arrives without you asking
Channels are outbound as well as inbound. Once one is connected, it's where AI Partner reaches you:
| What | When |
|---|---|
| Approval requests | An action needs your say-so — approve, edit or skip from the message |
| Proactive briefings | On your schedule — a morning brief, a market check, a weekly summary |
| Goal outcomes | A long-running goal finished, with its file attached |
| Job check-ins | A job has something to report, or needs an answer before it can continue |
Connect Telegram first even if you plan to live in another channel. Approvals are the thing you'll least want to be at your desk for.
Related
Different capability: replying from your own email, Slack and Telegram accounts, in your voice, with your approval gate.
What gets pushed to your channel, and when.
Messaging channels are AI Partner talking to you as itself. Human proxy is AI Partner talking to other people as you. They're configured separately and deliberately so.