What is claude-code-discord?

A Discord bot that brings Claude Code to your channels so you can chat, run shell/git, and manage branches. Access from any local, VM, or Docker instance with full capebilty of claude code!. It is open-source on GitHub.

Is claude-code-discord free to use?

claude-code-discord is open-source under the MIT license, so it is free to use.

What category does claude-code-discord belong to?

claude-code-discord is listed under devtools in the Claudeers registry of Claude-compatible tools.

claude-code-discord

Run Claude Code from Discord with full SDK integration, agents, rewind, mid-session controls and more.

Found a bug or have an idea for improvement? Submit it via GitHub Issues >⩊<

Feature	Details	Status
Use Claude Code Anywhere	Host locally (VM / Docker / cloud) and send commands via the Discord API	✅
Thread-per-session	Each `/claude-thread` conversation gets its own Discord thread with custom names	✅
Granular sandbox config	Full SDK sandbox with network rules, filesystem ACLs, and excluded commands	✅
Local hosting & security	Keep keys and code on your infra while exposing a controlled interface through Discord	✅
Centralized collaboration	Run commands and discuss results where your team already communicates	✅
Branch-aware organization	Maps Git branches to channels/categories so feature work stays separated	✅
Mid-session controls	Interrupt, change model, change permissions, stop tasks, and rewind without restarting	✅
MCP server management	View status, toggle, and reconnect MCP servers mid-session	✅
Hooks system	Passive SDK callbacks for tool use, notification, and task completion observability	✅
Full SDK Integration	Built on `@anthropic-ai/claude-agent-sdk` with native agent support	✅
Granular sandbox config	Full SDK sandbox with network rules, filesystem ACLs, and excluded commands	✅
AskUserQuestion	Claude can ask clarifying questions mid-session via Discord buttons	✅
Interactive permission prompts	Allow/Deny buttons when Claude wants to use unapproved tools	✅
Role-based access control	Restrict destructive commands (`/shell`, `/git`, worktree ops) to specific Discord roles	✅
Channel monitoring	Watch a channel for bot/webhook messages and auto-investigate in a thread	✅
Audit trail & accountability	Channel history provides an easy-to-search record of who ran what and when	✅

Feature Details Status Use Claude Code Anywhere Host locally (VM / Docker / cloud) and send commands via the Discord API ✅ Thread-per-session Each /claude-thread conversation gets its own Discord thread with custom names ✅ Granular sandbox config Full SDK sandbox with network rules, filesystem ACLs, and excluded commands ✅ Local hosting & security Keep keys and code on your infra while exposing a controlled interface through Discord ✅ Centralized collaboration Run commands and discuss results where your team already communicates ✅ Branch-aware organization Maps Git branches to channels/categories so feature work stays separated ✅ Mid-session controls Interrupt, change model, change permissions, stop tasks, and rewind without restarting ✅ MCP server management View status, toggle, and reconnect MCP servers mid-session ✅ Hooks system Passive SDK callbacks for tool use, notification, and task completion observability ✅ Full SDK Integration Built on @anthropic-ai/claude-agent-sdk with native agent support ✅ Granular sandbox config Full SDK sandbox with network rules, filesystem ACLs, and excluded commands ✅ AskUserQuestion Claude can ask clarifying questions mid-session via Discord buttons ✅ Interactive permission prompts Allow/Deny buttons when Claude wants to use unapproved tools ✅ Role-based access control Restrict destructive commands (/shell, /git, worktree ops) to specific Discord roles ✅ Channel monitoring Watch a channel for bot/webhook messages and auto-investigate in a thread ✅ Audit trail & accountability Channel history provides an easy-to-search record of who ran what and when ✅ preview

Quick Start

git clone https://github.com/zebbern/claude-code-discord.git
cd claude-code-discord
cp .env.example .env
# Edit .env with your DISCORD_TOKEN and APPLICATION_ID
docker compose up -d
# if not using ANTHROPIC_API_TOKEN:
docker exec -it claude-code-discord claude /login

Need a Discord bot token first? See Discord Bot Setup.

Installment options (auto setup script or manual installation), see Installation Guide.

Documentation

Doc	Description
Discord Bot Setup	Create a Discord app, get your token and application ID, invite the bot
Installation	Docker, one-command setup, manual setup, `.env` configuration
Commands	Full reference for all 45+ slash commands
Features	Thinking modes, agents, MCP, rewind, structured output, mid-session controls
Architecture	Project structure and SDK integration details
Docker	Docker Compose, GHCR images, Watchtower auto-updates
Updating	How to update (Docker pull, git pull, version check)

Select Newest Model Available

/settings category:claude action:set-model value:opus
/settings category:claude action:set-model value:sonnet
/quick-model model:haiku

Configuration

Create a .env file (or copy .env.example):

# Required
DISCORD_TOKEN=your_bot_token_here
APPLICATION_ID=your_application_id_here

# Optional
ANTHROPIC_API_KEY=sk-ant-...          # Enables dynamic model discovery & refresh
USER_ID=your_discord_user_id          # @mention when Claude finishes a task
CATEGORY_NAME=claude-code             # Discord category for bot channels
WORK_DIR=/path/to/project             # Working directory (default: current dir)

# Access Control (RBAC) — leave blank to keep all commands open
ADMIN_ROLE_IDS=123456789,987654321    # Comma-separated Discord role IDs
ADMIN_USER_IDS=111111111              # Comma-separated Discord user IDs

# Channel Monitoring (optional)
MONITOR_CHANNEL_ID=123456789012345678    # Channel to monitor for alerts from other bots/webhooks/users
MONITOR_BOT_IDS=987654321,111111111      # Comma-separated bot/webhook/user IDs to trigger auto-investigation

# Proxy (optional — respected automatically if set)
# HTTP_PROXY=http://proxy:8080
# HTTPS_PROXY=http://proxy:8080
# NO_PROXY=localhost,127.0.0.1

Variable	Required	Description
`DISCORD_TOKEN`	Yes	Bot token from the Discord Developer Portal
`APPLICATION_ID`	Yes	Application ID from the Developer Portal
`ANTHROPIC_API_KEY`	No	Enables dynamic model discovery; refreshes hourly
`USER_ID`	No	Your Discord user ID — bot @mentions you when tasks finish
`CATEGORY_NAME`	No	Discord category name for channels (default: `claude-code`)
`WORK_DIR`	No	Working directory for Claude operations (default: current dir)
`ADMIN_ROLE_IDS`	No	Comma-separated role IDs for RBAC (shell, git, system, admin)
`ADMIN_USER_IDS`	No	Comma-separated user IDs for RBAC — grants access regardless of roles
`MONITOR_CHANNEL_ID`	No	Discord channel ID to watch for bot/webhook messages
`MONITOR_BOT_IDS`	No	Comma-separated bot/webhook user IDs that trigger auto-investigation
`HTTP_PROXY`	No	HTTP proxy URL (also reads `http_proxy`)
`HTTPS_PROXY`	No	HTTPS proxy URL (also reads `https_proxy`)
`NO_PROXY`	No	Comma-separated hosts to bypass proxy

CLI flags override environment variables. Environment variables override .env file values.

Startup Options

# Standard start
deno task start

# Development mode (hot reload)
deno task dev

# Direct with environment variables
deno run --allow-all index.ts

# With optional flags
deno run --allow-all index.ts --category myproject --user-id YOUR_DISCORD_ID

Flag	Env Variable	Description
`--category <name>`	`CATEGORY_NAME`	Discord category name for channels (default: `claude-code`)
`--user-id <id>`	`USER_ID`	Your Discord user ID for mentions when tasks finish

CLI flags override environment variables. Environment variables override .env file values.

Channel Monitoring

Automatically investigate alerts from other bots or webhooks. When a monitored bot posts in the configured channel, the bot batches messages over a 30-second debounce window, creates a thread on the alert message, and streams Claude's investigation there.

Setup

Enable the Message Content intent — In the Developer Portal, go to your app → Bot → enable Message Content Intent. The bot needs this to read messages from other bots.
Get the channel ID — Right-click the channel in Discord (Developer Mode must be on) and copy the ID. Set MONITOR_CHANNEL_ID in .env.
Get the bot/webhook user IDs — The easiest way is to look at a message from the bot in the channel, right-click the author, and copy the ID. For webhooks, check the webhook's user ID in the channel's integration settings. Set MONITOR_BOT_IDS as a comma-separated list.
Bot permissions — Ensure the bot has these permissions in the monitored channel:
- Read Messages
- Create Public Threads
- Send Messages in Threads

Platforms	cli, api
Operating systems	—
AI compatibility	claude
License	MIT
Pricing	open-source
Language	TypeScript

claude-code-discord

claude-code-discord

Quick Start

Documentation

Select Newest Model Available

Configuration

Startup Options

Channel Monitoring

Setup

// compatibility

// faq

// embed badge

// retro hit counter

// reviews

// guestbook

// related in Integrations & Connectors