claude-multi-channel-discord: Skill for Claude Code

Run MCD on native Windows

On win32, MCD uses the headless backend: each channel runs as claude -p --input-format stream-json --output-format stream-json over pipes instead of in a tmux pane (src/claude-process.ts, src/claude-bin.ts). No WSL, tmux or Git Bash is needed. Background reading: docs/setup.md → "Windows".

All commands below run from the repo root in PowerShell. Windows PowerShell 5.1 is fine.

Never kill processes by name (taskkill /im claude.exe, Stop-Process -Name claude, or a filter on stream-json). The Claude desktop app runs its own claude.exe sessions, and this conversation may be one of them. MCD's children are the claude.exe processes whose command line contains mcd-<slug>-…\mcp-config.json. To stop MCD, use the scripts below.

If this session is itself running inside MCD (a project channel), don't stop or restart the bot. That ends your own session; see CLAUDE.md.

1. Check what's already done

Run these and skip the steps that are already satisfied:

$env:Path = [Environment]::GetEnvironmentVariable('Path','Machine') + ';' + [Environment]::GetEnvironmentVariable('Path','User')
bun --version; git --version
Test-Path "$HOME\.claude\channels\discord-multi\.env"          # setup done?
Get-ScheduledTask multi-channel-discord -ErrorAction SilentlyContinue | Select TaskName, State

Check that the claude CLI is logged in. The headless backend uses MCD_CLAUDE_BIN, then claude.exe on PATH, then the Claude desktop app's bundled CLI. The app is MSIX-packaged, so outside the app that CLI lives under %LOCALAPPDATA%\Packages\Claude_*\LocalCache\Roaming\Claude\claude-code\<ver>\<hash>\claude.exe.

bun -e "import('./src/claude-bin.ts').then(m => console.log(m.resolveClaudeBin()))"
& (bun -e "import('./src/claude-bin.ts').then(m => console.log(m.resolveClaudeBin()))") auth status

2. First-time setup

1. Tools: winget install --id Oven-sh.Bun -e --scope user and winget install --id Git.Git -e. The Git installer asks for admin (UAC); the user approves it. Then run bun install --no-summary.
2. Claude login: loggedIn: false above means the user must sign in. Open a terminal tab and run the resolved claude.exe with auth login. The user finishes it in the browser. Never handle their credentials yourself.
3. Discord bot: the user does this in the Developer Portal. Create an application. On the Bot tab, enable Message Content Intent, then use Reset Token. Invite it with scope bot and View Channels, Send Messages, Send Messages in Threads, Read Message History, Add Reactions and Manage Channels. With Developer Mode on in Discord, copy their user ID and the master channel ID.
4. State dir: start the setup in a terminal tab so the user types the values there. Never ask for the bot token in chat.