9af9bc947a
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>
75 lines
2.7 KiB
Markdown
75 lines
2.7 KiB
Markdown
---
|
|
name: add-discord-v2
|
|
description: Add Discord bot channel integration to NanoClaw v2 via Chat SDK.
|
|
---
|
|
|
|
# Add Discord Channel
|
|
|
|
Adds Discord bot support to NanoClaw v2. Discord is built in — no adapter package to install.
|
|
|
|
## Pre-flight
|
|
|
|
Check if `src/channels/discord.ts` exists and the import is uncommented in `src/channels/index.ts`. If both are in place, skip to Credentials.
|
|
|
|
## Install
|
|
|
|
Discord support is bundled with NanoClaw — there is no separate package to install.
|
|
|
|
### Enable the channel
|
|
|
|
Uncomment the Discord import in `src/channels/index.ts`:
|
|
|
|
```typescript
|
|
import './discord.js';
|
|
```
|
|
|
|
### Build
|
|
|
|
```bash
|
|
npm run build
|
|
```
|
|
|
|
## Credentials
|
|
|
|
### Create Discord Bot
|
|
|
|
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")
|
|
3. From the **General Information** tab, copy the **Application ID** and **Public Key**
|
|
4. Go to the **Bot** tab and click **Add Bot** if needed
|
|
5. Copy the Bot Token (click **Reset Token** if you need a new one — you can only see it once)
|
|
6. Under **Privileged Gateway Intents**, enable **Message Content Intent**
|
|
7. Go to **OAuth2** > **URL Generator**:
|
|
- Scopes: select `bot`
|
|
- Bot Permissions: select `Send Messages`, `Read Message History`, `Add Reactions`, `Attach Files`, `Use Slash Commands`
|
|
8. Copy the generated URL and open it in your browser to invite the bot to your server
|
|
|
|
### Configure environment
|
|
|
|
All three values are required — the adapter will fail to start without `DISCORD_PUBLIC_KEY` and `DISCORD_APPLICATION_ID`.
|
|
|
|
Add to `.env`:
|
|
|
|
```bash
|
|
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`
|
|
|
|
## Next Steps
|
|
|
|
If you're in the middle of `/setup`, return to the setup flow now.
|
|
|
|
Otherwise, run `/manage-channels` to wire this channel to an agent group.
|
|
|
|
## Channel Info
|
|
|
|
- **type**: `discord`
|
|
- **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 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
|
|
- **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.
|