Skip to main content

​
Discord

Discord works well for personal servers, community servers, and lightweight mobile workflows.

​
What you get

  • Talk to a local coding agent from any Discord channel.
  • Keep conversations separate — Avibe opens a new thread per task to mirror Slack-style sessions.
  • Route selected channels to selected agent backends.
  • Receive progress and completion updates. CLI agents stream text as they write it; Vibey posts each step when it completes.

​
Set up the bot

  1. Open the Discord Developer Portal → New Application and name it.
  2. Go to Bot → Add Bot and copy the Bot token.
  3. Under Bot → Privileged Gateway Intents, enable Message Content Intent (required). Server Members Intent is optional.
  4. Under OAuth2 → URL Generator, select the bot scope and these permissions: View Channels, Send Messages, Create Public Threads, Send Messages in Threads, Add Reactions, Attach Files. Open the generated URL and invite the bot to your server.
  5. In Settings > Messaging Platforms > Platform Connections, choose Discord, paste the bot token, and Validate. Then, under Groups, pick your server and enable channels.
The most common Discord miss is leaving Message Content Intent off — the bot connects but never sees message text. For DMs, Discord has no threads, but sessions are still isolated per message.

​
Smoke test

Send a short message in an enabled Discord channel:
Then run locally:

​
Outbound proxy

When the host running Avibe cannot reach Discord directly, set proxy_url on the Discord config block from the Web UI. Both HTTP/HTTPS proxies and SOCKS proxies are supported (any socks*:// scheme — socks4, socks4a, socks5, or socks5h). Saving the config block only persists the change; run vibe restart --delay-seconds 60 afterwards so the new transport applies to live connections.

​
Common issues