Telegram linking

Link your Telegram account to your Busymate identity so the bot knows who you are. Once linked, the BusyBro assistant greets you by name and tailors every answer to your role — and capability-gated write actions become available at your permission level. See what BusyBro can do in the BusyBro ask API.

TL;DR

The flow

1. Run /login in the Busymate Telegram bot.
2. The bot replies with a one-time dash.busymate.net/account?tglink=<code> link.
3. Open the link in a browser where you're signed in to the dashboard. The /account page's Telegram tab reads the tglink query param and consumes the code, binding your Telegram account to your signed-in Busymate user.
4. The bot confirms the link. From then on the bot knows your identity and role.

If you open the link without being signed in, you'll be sent through /login first, then bounced back to /account to finish — the code is still consumed by the Telegram tab.

Managing the link from the bot

What linking changes

• BusyBro greets you by name and tailors answers to your role — a viewer gets read-only guidance; a user with edit capabilities sees the write actions they're allowed to run.
• Capability-gated writes become available to you in chat at your role level, scoped to devices you own (set Live Activity message, rename device, VPN on/off, connection type, service groups, tags). Destructive fleet operations are never exposed. Full detail in BusyBro ask API.

Downstream: BusyBro inherits your identity & role

Linking is the gate for everything BusyBro (the /ask assistant) does on your behalf — once /me shows your identity, the assistant resolves your Busymate user and applies your role's capabilities to every turn:

• Read help respects your capabilities. BusyBro answers about the sections your role can view; it won't surface data or guidance for areas you have no access to.
• Write actions run only at your level — and only on your devices. A capability-gated action (rename device, VPN on/off, connection type, Live Activity message, service groups, tags) fires only if your role grants the matching edit capability, and only against devices you own.
• Destructive fleet operations are never exposed. Unpair, wipe, send-push, role mutations and the like are never offered through chat, regardless of role.

Until you link, BusyBro has no identity to bind to and stays read-only/anonymous. See BusyBro ask API for the full capability surface.

Programmatic parity (MCP)

The same link lifecycle is exposed as tools on the busymate-net MCP server:

{"jsonrpc":"2.0","id":1,"method":"tools/call",
 "params":{"name":"link_telegram","arguments":{"code":"<code-from-/login>"}}}

{"jsonrpc":"2.0","id":2,"method":"tools/call",
 "params":{"name":"unlink_telegram","arguments":{"confirm":true}}}

Troubleshooting