Five-minute setup. Pick the channels Ergod is allowed in, optionally gate by role, and you're done. No webhook plumbing, no backend to host.
Don't own a server you can install bots on? Skip this page - try Ergod free in our community. No add-to-server required.
Discord OAuth flow. You'll need Manage Server on the server you're adding it to.
Click Add to your server above. Discord will ask you to pick a server you have Manage Server on. If you're inviting Ergod for someone else, send them this page - only a server admin can complete the install.
Discord shows the exact permission set Ergod is asking for. The defaults are read-and-respond + thread management - nothing destructive, no kick/ban, no admin. Full breakdown below. You can tighten further by limiting the bot's role to specific channels.
By default Ergod will respond anywhere it can see messages and an @-mention. Most servers want to scope it tighter. Two options:
View Channel + Send Messages in the channels you want./ergod-config channel action:allow channel:#dev-help from any text channel - explicit allowlist, stacks across multiple channels, persists across role edits./ergod-config threads mode:always. Ergod will reply in a thread off the trigger message instead of cluttering the channel.In one of the allowed channels, type @Ergod what can you do? The first response after install will take ~15-20s while your container provisions. Warm replies typically land in ~5s. Free tier gives every user a daily usage budget plus a one-time welcome boost worth 3 days of Free's daily usage that never expires - so your first few days are on us.
Some teams want to restrict who can use the bot, or unlock the Pro tier (5× Free's daily usage, sub-agent dispatch, priority cold start, model picker, channel-shaped personas). Any tier — Free included — can plug in a Claude / GPT / Gemini / OpenRouter key with /byok set for ~5× more turns at the cap.
/ergod-config role action:block role:@Read-Only - block a role from invoking Ergod. Use action:unblock to reverse.Discord groups permissions into a single OAuth grant. Below is every individual permission inside the install URL, explained one by one. Notably absent: Manage Server, Manage Channels, Kick, Ban, Mention Everyone, Administrator.
These are gated behind the Discord Manage Server permission. Server members without it won't see them in the slash-command picker. The full command list (including end-user commands) lives on the commands page.
Allowlist or blocklist a specific channel. Once any channel is allow-listed, all others are off by default. Stacks.
Block a role from invoking Ergod, or unblock a previously-blocked one. Blocklist only - no role allowlist.
Whether Ergod creates a thread for each reply across the whole server.
Override thread mode for the current channel. default returns to the server-wide setting.
Toggle scrubbing of @everyone, @here, and role pings in Ergod's replies.
How Ergod tells users they're blocked - ephemeral notice or no reply at all.
Print the current server-wide config (allowed channels, blocked channels, blocked roles, thread mode, mention scrub).
The short version. Full detail lives in privacy and how it thinks.
Each user gets a Docker container scoped to their workspace. No cross-tenant access; ALL caps dropped, no-new-privileges enforced, RFC1918 + cloud metadata blocked at egress.
/export ships your workspace as a zip. /reset clears history; /workspace factory-reset rebuilds the container from scratch.
Ergod only reads messages that @-mention it, DM it, or are inside a thread it's already in. We don't scrape channel history, members, or unrelated messages.
Linked GitHub tokens are encrypted with Fernet (AES-128-CBC + HMAC-SHA256), scoped per-owner, and never written to your workspace filesystem.
Or come hang out in the community Discord first - we'll happily walk you through it.