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.
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 allow:#dev-help from any text channel — explicit allowlist, supports multiple channels, persists across role edits./ergod-config thread-mode on. 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 ~15s while your container provisions. Subsequent messages land in 8–12s. Free tier is 5 commands per user per day, no card needed.
Some teams want to restrict who can use the bot, or unlock the Pro tier (200 commands/day, sub-agent dispatch, priority cold start, premium model routing).
/ergod-config role allow:@Engineers — only members of that role can invoke Ergod. Stack multiple role allow calls for an OR-list./ergod-config role block:@Read-Only — explicit deny that overrides allows.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. Allowlist takes precedence when both are set.
Restrict Ergod to specific roles, or block a role from invoking it. Stackable.
When on, Ergod replies in a fresh thread off the trigger message instead of in-channel.
Print the current server-wide config (allowed channels, roles, thread mode).
Reset all server-wide config back to defaults. Requires Manage Server.
Aggregate usage and remaining quota for the whole server. Useful for capacity planning.
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.