docs/usage/messenger/discord.mdx
Discord works in two phases: a server admin adds the official LobeHub bot to a Discord server once, and then each member links their personal Discord account to LobeHub. Both phases happen from Settings → Messenger → Discord.
The Discord install audit is per-server, but your personal link is global to your Discord account — you only link once, and the same link works in every server that has the bot.
In LobeHub, open Settings → Messenger and click the Discord card. Click Connect in the top-right.
You'll be redirected to Discord's bot-add screen. Pick the server you want to add the bot to and click Authorise.
After approval you're redirected back to LobeHub. The server appears as a server row in Connections.
Server already connected by someone else? LobeHub shows a "Server already connected" notice. You don't need to add the bot again — just DM the LobeHub bot in Discord to link your personal account.
</Steps>
Open the LobeHub bot in Discord — the Open in Discord button on the Discord detail page (or the pending-link row) takes you straight there.
In the bot DM, send any message to trigger the linking flow. The bot replies with a one-time confirmation link.
Tap the link, sign in to LobeHub if asked, and choose a default agent. Every message you DM the LobeHub bot in Discord (across all servers) will route to this agent.
Your link appears as a user row in Connections. </Steps>
Two equivalent ways:
/agents and pick a different agent.The change takes effect on the next message you send.
Discord has two distinct disconnect actions, with one important difference from Slack:
| Action | Effect |
|---|---|
| Disconnect on a user row | Unlinks your LobeHub account from your Discord account. The bot stops accepting your DMs until you message it and link again. |
| Disconnect on a server row | Removes the install audit entry only. The bot stays in the Discord server until a server admin manually kicks it. Other people's personal links are unaffected. |
You can re-add the bot to a server (or re-link personally) at any time by repeating the relevant phase.
<reason>) — Common reasons: authorisation cancelled, install session expired (re-open the modal and try again), Discord returned incomplete data (retry; if persistent, contact support).