Run Claude Code from Discord. It executes on your machine and stays reachable from any channel.
The Telegram version proved remote coding could work. But once you have more than one project, one chat becomes noise. Discord already solves that with channels and threads.
Thread branching came from the architecture, not a gimmick. Start a thread, inherit parent context, and optionally attach a worktree. Parallel tasks stay separate without losing context.
Same channels, same notifications, same search — with actual repo access added.
Read the original threadIf your server already runs bots, this fits in cleanly. Keep planning, research, deploy bots, and Claude Code in one workspace instead of splitting across tools.
Discord gives you channels, threads, commands, search, and mobile notifications out of the box. That's the scaffolding async code work actually needs.
Each project gets its own working directory, session, and settings.
Create a thread to branch work without dropping parent context.
Start from phone, get notified on completion, and review results anywhere.
Claude Code reads the codebase, runs commands, manages git, and executes tests. This is execution, not generic suggestions.
claude-on-discord puts that capability in the same place your team already works. Start a task, check progress later, continue from any device.
Keep Claude Code alongside research, deploy, and ops bots in the same server. Clear lanes, less tool switching.
Try risky work in a thread first. Keep it, merge it, or drop it without destabilizing the main lane.
Runs continue on your machine until complete. You get updates in Discord and can interrupt when needed.
SSH and terminal apps still expect constant attention. Discord is already on your phone, handles reconnects, and pushes notifications. It fits async work better.
Create a thread and keep parent context. Optional worktree for clean parallel changes.
Each channel keeps its own working dir, model, history, and system prompt.
One bot, multiple servers. Configure with DISCORD_GUILD_IDS.
In shared guild channels, runs require explicit mention. No random wakeups.
Stream output in one message with Interrupt and Abort controls.
/pr open, draft, status, merge from Discord.
Set different behavior per channel and keep it persistent.
Automatically loads .claude/mcp.json from your project.
/bash and !command for direct command execution.
/diff sends a patch file so review works cleanly on mobile.
# Clone and install
git clone https://github.com/spanishflu-est1918/claude-on-discord
cd claude-on-discord && bun install
# Interactive setup: writes .env, prints invite URL
bun run setup
# Start
bun start.env, generates your bot invite URL.What's live and what's next.
One bot can run across multiple Discord servers with DISCORD_GUILD_IDS.
In shared guild channels, runs require an explicit @hermes_claude mention.
Thread-level git worktrees for isolated parallel work.
Collect key constraints first, then run with a clear plan.
Install and bootstrap without cloning the repo.
Optional OpenAI Codex backend per channel.
Suggest and create thread forks based on task size and risk.
Route signed external events directly into target channels.
Track spend and turn volume by server, channel, and model.