discord

multi-channel-discord

Project-aware Discord bot for Claude Code. One Discord bot, many isolated channels — each channel gets its own Claude Code subprocess, system prompt, conversation history, and git working tree.

Forked from anthropics/claude-plugins-official/external_plugins/discord (Apache-2.0). Backwards-compatible with upstream when no channels.json is present.

---

What it adds vs upstream

	upstream	this fork
Message routing	one Claude session for all messages	per-channel Claude subprocess (lazy spawn, idle eviction)
System prompt	global (CLAUDE.md in cwd)	per channel (projects/<slug>/CLAUDE.md)
Conversation history	global	per channel (--resume across restarts)
Provisioning	manual config	!project create/clone/... from a master Discord channel
Git integration	—	clone repos, push branches, open PRs via Octokit / Azure DevOps REST
Provider routing	Claude subscription only	per-project routing to any Anthropic-compatible API (MiniMax, Bedrock, etc.)
Auth	Claude Code subscription	same — never API key

---

How it works

Discord (one bot) ─→ server.ts ─→ ProjectPool ─→ N × claude subprocesses
                          │              │              │
                          │              │              └── HTTP MCP →─┐
                          │              ├── Map<chat_id, process>      │
                          │              └── lazy spawn / idle evict    │
                          └── MasterMcpServer ←─────────────────────────┘
                                  └── one HTTP server, multiplexed by /mcp/<chat_id>

• Each project channel → one claude subprocess inside a detached tmux session.
• Inbound: Discord messages injected via tmux send-keys (keeps the warm interactive session).
• Outbound: Claude calls mcp__mcd__reply against the HTTP MCP server → Discord, chunked at 2000 chars.
• Cross-platform: HTTP-on-localhost works identically on Linux, macOS, and Windows.

---

Quick start

1. Prerequisites: bun, claude CLI (logged in), tmux, git. Optionally gh for PR workflows.

bin/check-env.sh   # verify everything is installed

2. Clone and install:

git clone https://github.com/chan4lk/claude-multi-channel-discord ~/dev/multi-channel-discord
cd ~/dev/multi-channel-discord
bun install

3. Create a Discord bot at discord.com/developers/applications:

• Enable Message Content Intent in the Bot tab.
• OAuth2 → URL Generator: scope bot, permissions: View Channels, Send Messages, Send Messages in Threads, Read Message History, Add Reactions, Manage Channels.
• Invite the bot to your server. Copy your User ID and the master channel ID (requires Developer Mode).

4. Bootstrap:

bin/setup-new-instance.sh \
  --state-dir ~/.claude/channels/discord-multi \
  --user-id   <your-discord-user-id> \
  --master    <master-channel-id> \
  --slug      master \
  --prompt    "You are the master controller. Be terse." \
  <<< "$DISCORD_BOT_TOKEN"

5. Run:

MCD_CHANNELS_DIR=~/.claude/channels/discord-multi bun server.ts

In the master Discord channel:

!project help
!project list

6. Create your first project channel (from the master channel):

!project create --new-channel my-project --slug my-project --prompt "You are a helpful coding assistant."

Or clone a repo into a channel:

!project clone --new-channel my-repo --slug my-repo --repo https://github.com/owner/repo.git --creds github-pat --prompt "You work in the my-repo repository."

---

WhatsApp setup (optional)

⚠️ Unofficial client — ToS risk: WhatsApp support is powered by Baileys, an unofficial WhatsApp Web library. Use violates WhatsApp's Terms of Service and can result in your number being permanently banned. Only use with a personal or dedicated self-hosted account.

1. Enable: Create the auth directory before starting the server:

mkdir -p ~/.claude/channels/discord-multi/whatsapp-auth
chmod 700 ~/.claude/channels/discord-multi/whatsapp-auth

Or set WHATSAPP_ENABLED=1 in your environment. Either way, the adapter activates on the next server start.

2. Pair: On first run the bot posts a QR code image to your master Discord channel. Open WhatsApp on your phone → Linked Devices → Link a Device, and scan the QR within 60 seconds. The session is then saved to whatsapp-auth/ and persists across restarts.

3. Bind a project: In channels.json, set platform and whatsappJid on the project entry:

{
  "projects": {
    "<chat_id>": {
      "slug": "my-whatsapp-project",
      "platform": "whatsapp",
      "whatsappJid": "[email protected]"
    }
  }
}