How it feels
#general
you @Claude our deploy script keeps timing out, any ideas? 📎 deploy.sh
Claude 👀
└─ 🧵 "our deploy script keeps timing out…"
Claude Looking at your script, three things stand out… ▌ ← grows live
you can you rewrite it with retries?
Claude Sure — here's the updated script: … ✅
One mention opens a thread. Everything in that thread is one conversation —
Claude remembers all of it, even across bot restarts.
Features
| |
|---|
| 🧵 Threads with memory | Every conversation maps to a persistent Claude session (resume under the hood) |
| 🔑 Per-user subscription auth | Each member runs /link-claude and pastes their own claude setup-token output. No shared token, no shared limits |
| ⚡ Streaming feel | 👀 → live-growing reply → ✅. Code fences are never split across messages |
| 📎 Attachments | Send text files and images; long answers come back as response.md |
| 🎛️ Admin dashboard | Setup wizard, channel/role allowlists, live sessions, usage stats — in a Claude×Discord themed UI |
| 🤖 Agentic mode (opt-in) | File & shell tools in per-thread sandboxes. Off by default, admin-gated, Docker-first |
| 🐙 Per-user GitHub (opt-in) | Members /link-github their own account; agentic threads clone, push & open PRs as them, via git/gh |
| 🚦 Limit-aware | Per-user queue, friendly "resets at 3pm" messages, /usage command |
| 🐳 One-container deploy | docker compose up -d and you're live |
Quickstart
You need: Docker and 5 minutes. Each member who talks to the bot will need their own Claude
Pro/Max subscription (or Anthropic Console access) to run claude setup-token.
# 1. Discord app → Bot page → enable Message Content Intent, then:
git clone https://github.com/t11z/claudecord.git
cd claudecord
cp .env.example .env # set DISCORD_BOT_TOKEN and DISCORD_APPLICATION_ID
docker compose up -d
# 2. Invite the bot (no dashboard needed — just the application ID)
open "https://discord.com/oauth2/authorize?client_id=YOUR_APPLICATION_ID&scope=bot%20applications.commands&permissions=397552861248"
# 3. In Discord: sign into the dashboard and link your subscription
/dashboard # replies with a one-time sign-in link
/link-claude link # opens a modal — paste the output of `claude setup-token`
Then mention the bot in any channel. That's it — there's no dashboard password anywhere;
signing in is always a one-time link from /dashboard.
📚 Full documentation → — setup
guides, configuration reference, security notes and maintainer docs.
Commands
| Command | |
|---|
@Claude … | Start a conversation (opens a thread) |
/ask | One-shot question, optionally private |
/reset | Make Claude forget the current thread |
/usage | Server usage & queue stats |
/model | Sonnet / Opus / Haiku for new threads (admin) |
/config | Allowlists, agentic mode, on/off (admin) |
/link-claude | Connect your own Claude subscription — required before the bot will run for you |
/link-github | Connect your own GitHub account for agentic runs (optional) |
/dashboard | Get a one-time sign-in link for the web dashboard |
A note on security & fair use
- Agentic mode gives Claude shell access inside a sandbox. It's off by
default for a reason — read the
security docs
before enabling it, and run the bot in Docker.
- claudecord has no shared, instance-wide Claude credential. Every run is
billed to the Discord user who started it, via their own
/link-claude.
You self-host the infrastructure (the Discord bot); each member brings their
own subscription and their own rate limits.
Contributing
Contributions are very welcome — this project is deliberately built to be
hackable: TypeScript everywhere, no ORM, no framework magic, pure functions
where it counts, and a documented
architecture.
npm install && npm run dev # bot
npm run dev:dashboard # dashboard with hot reload
npm test # no tokens needed
License
MIT — do whatever makes your server happier.
