>_ For Developers · Hosted · Shared-Server NativeErgod is an AI coding agent built for Discord — not a CLI ported to it. Hosted, multi-user by default, per-user isolated workspaces, no credentials to manage. A cloud alternative to Claude Code Channels and OpenClaw that works in under 30 seconds cold and 10–15 seconds per message once your container is warm.
Live — @ the bot in #general and watch it build. Non-dev version of this page →
Capabilities
50+ built-in tools, selected automatically by the agent. Runs in a sandboxed per-user container with persistent state — warm responses land in 10–15 seconds.
Python, JavaScript, TypeScript, HTML/CSS, Go, Rust. Executes in a sandboxed workspace and streams results back to Discord.
Every Discord user gets a private Docker container. Files persist between sessions. Individual collaborators are opt-in via /collab add on Pro.
Admins open a /ergod-config channel-session in any channel and nominate a Pro user to sponsor it. Everyone in the channel then reads and writes one shared workspace together — distinct from /collab, which invites individuals to your own workspace. 90-day sponsor renewal; auto-freeze if the sponsor lapses.
/session new, /session load, /session list. Switch between a bug hunt and a side project without losing either — names auto-generate.
/ergod-config gates reply behavior by channel, role, mentions, and thread mode. Permissioned to Discord's manage_channels — no extra role to add.
/github link with a PAT; Ergod validates it against the API and stores it encrypted at rest. Token never touches the container filesystem — git reads it from an ephemeral, turn-scoped credential helper.
/stats, /context, /compact, /diff, /undo, /usage. Inspect session size, roll back the last file write, check daily quota.
Attach screenshots, diagrams, or design refs to any message. Fallback vision model handles it if the main model can't.
Plug any Model Context Protocol server into your workspace. /mcp add for remote streamable-HTTP; /mcp add-stdio for stdio servers that run inside your sandbox — one-click installer for common launchers (npx, uvx). Tools surface as agent tool calls automatically; crashed stdio servers are detected and surfaced for recovery.
/workspace reset wipes files and keeps the container. /workspace factory-reset tears down and rebuilds the container from scratch when you want a known-clean base.
Claude, GPT, Gemini, OpenRouter. Model choice lands on Pro first; free stays on the standard hosted model. Full command reference →
Reliability & isolation
Ergod is multi-tenant by design. Isolation isn't a setting — it's the default, and it's enforced at the network boundary, not just at the filesystem.
Every tenant boots into their own sandboxed container. Filesystem, processes, and shell state don't cross tenants. Cold boot under 30 seconds; subsequent messages land warm in 10–15 seconds.
Container egress blocks RFC1918 ranges, SMTP, and non-DNS UDP. Agents can reach the public internet but can't pivot into internal services or fan out unsolicited mail.
Concurrent background tasks are capped per tenant so one workspace can't monopolize the fleet. An operator audit log records admin-side actions.
Linked GitHub PATs are encrypted at rest and only surface as env vars on the owner's own git invocations — scoped to a single turn. Never written to disk inside the container, never exposed to collaborators.
The system prompt is hardened against extraction and injection attempts. Recurring red-team passes drive the rules — specifics stay private so the defenses keep working.
Routine audits close fall-through paths between sandboxed tools and the host. Tool execution stays inside the container by construction; if the sandbox isn't available, the tool refuses rather than degrading to host execution.
US-based infrastructure. Container images, workspace volumes, and session state live in the US region unless otherwise noted.
vs Claude Code Channels & OpenClaw
If you've already ruled out a CLI bridge or a self-hosted stack, here's the side-by-side. Ergod is built for the way Discord actually works: many users, one server, independent workspaces.
| Ergod | Claude Code Channels | OpenClaw | |
|---|---|---|---|
| Runs without local setup | Yes — fully hosted | No — needs local CC session | No — self-hosted |
| Multi-user in a shared server | Yes — per-user workspaces | Bridges one user's session | Single-deployment |
| Multi-provider models | Rolling out to Pro | Anthropic only | Depends on your keys |
| Named sessions, switchable | Yes — /session new/load/list |
Single session, local FS | No first-class concept |
| Admin channel & role controls | Yes — native Discord perms | n/a | Operator-configured |
| Multi-user collaboration | Yes — Pro /collab add |
n/a (single user) | Self-host decides |
| Shared team workspace in a channel | Yes — Pro-sponsored channel sessions | n/a | Self-host decides |
| Persistent workspace per user | Yes | Tied to your local FS | Shared filesystem |
| Time to first message | <30s cold, 10–15s warm | Install + config + login | VPS + deploy + keys |
Ergod is not affiliated with Anthropic or OpenClaw. Comparison reflects public documentation of each product.
FAQ
/collab add @user on Pro grants a specific Discord user read/write access to your own workspace; they use /workspace switch to enter and /workspace current to confirm. Collaborators don't inherit your GitHub push credentials — their git auth fails cleanly unless they link their own account. Removal clears their stale workspace pointer automatically. Channel-wide — /ergod-config channel-session open opens a shared Ergod workspace that everyone in the channel reads and writes to together, sponsored by a Pro user who accepts via an Accept / Decline prompt. See the next question for the operational details.manage_channels) runs /ergod-config channel-session open and nominates a Pro user as sponsor; an Accept / Decline prompt lands for the sponsor, and the session only activates on accept. After that, every user in the channel routes into the same shared workspace — any message, any session, any file. Sessions renew every 90 days via an accept / snooze / don't-ask prompt; if the sponsor lapses from Pro, the channel session auto-freezes (read-only) until a new sponsor accepts. Admins can permanently blocklist a user or a whole channel with /ergod-config channel-session block. Closed sessions are retained for 90 days in case you re-open them.Join the Discord, @ the bot in #general, and ship something in the next five minutes.