> ## Documentation Index
> Fetch the complete documentation index at: https://docs.avibe.bot/llms.txt
> Use this file to discover all available pages before exploring further.

# Discord

> Connect Discord channels to Claude Code, OpenCode, or Codex through Avibe.

# 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 streamed progress and completion updates.

## Set up the bot

1. Open the [Discord Developer Portal](https://discord.com/developers/applications) → **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 the Avibe wizard, choose **Discord**, paste the bot token, **Validate**, 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:

```text theme={null}
Say hello and tell me what backend you are using.
```

Then run locally:

```bash theme={null}
vibe status
```

## 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

| Symptom                           | Check                                                                |
| --------------------------------- | -------------------------------------------------------------------- |
| Bot silent                        | Bot token, server install, channel selection                         |
| Bot connects but ignores messages | **Message Content Intent** is enabled in the Developer Portal        |
| Messages arrive but no response   | Agent backend enabled and CLI path valid                             |
| Wrong project                     | Channel routing and default working directory                        |
| Discord unreachable from host     | `proxy_url` on Discord config; check firewall and TLS errors in logs |