fix(discord-v2): document required DISCORD_PUBLIC_KEY and APPLICATION_ID

The Discord adapter fails to start without all three env vars. Also
fix platform ID format docs to show discord:{guildId}:{channelId}.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Gabi Simons
2026-04-09 13:57:28 +00:00
parent 69939b7774
commit 9af9bc947a

View File

@@ -35,20 +35,25 @@ npm run build
1. Go to the [Discord Developer Portal](https://discord.com/developers/applications) 1. Go to the [Discord Developer Portal](https://discord.com/developers/applications)
2. Click **New Application** and give it a name (e.g., "NanoClaw Assistant") 2. Click **New Application** and give it a name (e.g., "NanoClaw Assistant")
3. Go to the **Bot** tab and click **Add Bot** if needed 3. From the **General Information** tab, copy the **Application ID** and **Public Key**
4. Copy the Bot Token (click **Reset Token** if you need a new one — you can only see it once) 4. Go to the **Bot** tab and click **Add Bot** if needed
5. Under **Privileged Gateway Intents**, enable **Message Content Intent** 5. Copy the Bot Token (click **Reset Token** if you need a new one — you can only see it once)
6. Go to **OAuth2** > **URL Generator**: 6. Under **Privileged Gateway Intents**, enable **Message Content Intent**
7. Go to **OAuth2** > **URL Generator**:
- Scopes: select `bot` - Scopes: select `bot`
- Bot Permissions: select `Send Messages`, `Read Message History`, `Add Reactions`, `Attach Files`, `Use Slash Commands` - Bot Permissions: select `Send Messages`, `Read Message History`, `Add Reactions`, `Attach Files`, `Use Slash Commands`
7. Copy the generated URL and open it in your browser to invite the bot to your server 8. Copy the generated URL and open it in your browser to invite the bot to your server
### Configure environment ### Configure environment
All three values are required — the adapter will fail to start without `DISCORD_PUBLIC_KEY` and `DISCORD_APPLICATION_ID`.
Add to `.env`: Add to `.env`:
```bash ```bash
DISCORD_BOT_TOKEN=your-bot-token DISCORD_BOT_TOKEN=your-bot-token
DISCORD_APPLICATION_ID=your-application-id
DISCORD_PUBLIC_KEY=your-public-key
``` ```
Sync to container: `mkdir -p data/env && cp .env data/env/env` Sync to container: `mkdir -p data/env && cp .env data/env/env`
@@ -63,7 +68,7 @@ Otherwise, run `/manage-channels` to wire this channel to an agent group.
- **type**: `discord` - **type**: `discord`
- **terminology**: Discord has "servers" (also called "guilds") containing "channels." Text channels start with #. The bot can also receive direct messages. - **terminology**: Discord has "servers" (also called "guilds") containing "channels." Text channels start with #. The bot can also receive direct messages.
- **how-to-find-id**: Enable Developer Mode in Discord (Settings > App Settings > Advanced > Developer Mode). Then right-click a server or channel and select "Copy ID." - **how-to-find-id**: Enable Developer Mode in Discord (Settings > App Settings > Advanced > Developer Mode). Then right-click a server and select "Copy Server ID" for the guild ID, and right-click the text channel and select "Copy Channel ID." The platform ID format used in registration is `discord:{guildId}:{channelId}` — both IDs are required.
- **supports-threads**: yes - **supports-threads**: yes
- **typical-use**: Interactive chat — server channels or direct messages - **typical-use**: Interactive chat — server channels or direct messages
- **default-isolation**: Same agent group for your personal server. Separate agent group for servers with different communities or where different members have different information boundaries. - **default-isolation**: Same agent group for your personal server. Separate agent group for servers with different communities or where different members have different information boundaries.