9633788a1b
@chat-adapter/discord@4.27.0 includes vercel/chat#256, which fixes the Discord adapter unconditionally setting payload.content alongside payload.embeds when posting a card. In 4.26.0 every Discord card appeared twice (text content above the embed, identical content inside the embed) — every new install reproduced this on the welcome tour and on every approval card. The other 7 skills bump in lockstep because @chat-adapter/discord@4.27.0 depends on chat@4.27.0 while @chat-adapter/<other>@4.26.0 depend on chat@4.26.0. Mixing the cohort produces a TypeScript dual-version conflict between the bridge and adapter ChatInstance types. Files updated (one line per file in each pnpm install command): - add-discord (the user-visible bug fix) - add-gchat, add-github, add-linear, add-slack, add-teams, add-telegram, add-whatsapp-cloud (cohort consistency) Out of scope: add-imessage, add-matrix, add-webex, add-resend use third-party packages with independent versioning. Closes #2264
99 lines
3.2 KiB
Markdown
99 lines
3.2 KiB
Markdown
---
|
|
name: add-discord
|
|
description: Add Discord bot channel integration via Chat SDK.
|
|
---
|
|
|
|
# Add Discord Channel
|
|
|
|
Adds Discord bot support via the Chat SDK bridge.
|
|
|
|
## Install
|
|
|
|
NanoClaw doesn't ship channels in trunk. This skill copies the Discord adapter in from the `channels` branch.
|
|
|
|
### Pre-flight (idempotent)
|
|
|
|
Skip to **Credentials** if all of these are already in place:
|
|
|
|
- `src/channels/discord.ts` exists
|
|
- `src/channels/index.ts` contains `import './discord.js';`
|
|
- `@chat-adapter/discord` is listed in `package.json` dependencies
|
|
|
|
Otherwise continue. Every step below is safe to re-run.
|
|
|
|
### 1. Fetch the channels branch
|
|
|
|
```bash
|
|
git fetch origin channels
|
|
```
|
|
|
|
### 2. Copy the adapter
|
|
|
|
```bash
|
|
git show origin/channels:src/channels/discord.ts > src/channels/discord.ts
|
|
```
|
|
|
|
### 3. Append the self-registration import
|
|
|
|
Append to `src/channels/index.ts` (skip if the line is already present):
|
|
|
|
```typescript
|
|
import './discord.js';
|
|
```
|
|
|
|
### 4. Install the adapter package (pinned)
|
|
|
|
```bash
|
|
pnpm install @chat-adapter/discord@4.27.0
|
|
```
|
|
|
|
### 5. Build
|
|
|
|
```bash
|
|
pnpm 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.
|