Every slash command Ergod supports in Discord — grouped, documented, and example-driven. Most people never touch these: just @-mention the bot and describe what you want. The reference is here when you need it.
Type /help in Discord for the same list in-server.
Start here
Ergod is an agent, not a command grid. You don't need slash commands to use it — plain English works everywhere.
@Ergod in any channelMention the bot with your request. Works in any text channel Ergod has access to.
DM the bot directly. Available on every tier. Nothing you send is visible to other users.
Reply to any of Ergod's messages to continue a thread of conversation without re-mentioning.
Daily essentials
Stateless, no-argument commands for nudging the current conversation. Most days, these and an @-mention are all you need.
Start a fresh conversation (clears your current session). Shorthand for /session reset. Use /session new if you want to keep the old one around.
Show your daily usage stats — commands remaining today against your tier's quota.
Show how big the conversation has gotten. Useful before a long task so you know if you should /compact first.
Summarize the conversation so far to free up context. Needs at least 4 messages of history to do anything useful.
Undo Ergod's last file edit.
Show files Ergod created or changed this session. Works from the session's checkpoint stack, not git.
Show your session — messages, turns, and tokens used.
Show the in-Discord command list.
Session management
/sessionSave, switch between, rename, and delete conversations. Sessions persist across bot restarts and are isolated to your user. Names auto-generate from the first few messages so you don't have to think about them.
Show details of your current session — name, message count, when it was last used.
List your saved sessions, active first. Use the name or ID from here with /session load.
Save your current session and start a fresh one. Useful when you switch from one project to another.
Switch to a saved session by name or ID. Your current conversation is saved automatically first.
Rename your current session. Useful after the auto-name settles and you want something more descriptive.
Permanently delete one of your saved sessions. Cannot be undone.
Clear the conversation history for your current session without deleting it. Same thing /reset does — kept here so it's discoverable inside the session group.
Show the channel sessions you're sponsoring as a Pro user — which guild, which channel, and when each comes up for 90-day renewal. See Channel sessions for what these are.
GitHub
/githubLink a GitHub account so Ergod can commit, push, and open pull requests on your behalf. Tokens are stored encrypted per user.
Connect your GitHub account with a Personal Access Token. Tokens must start with ghp_ or github_pat_; Ergod validates against GitHub before storing.
Disconnect your GitHub account. The stored token is deleted immediately.
Check your linked GitHub account — shows the account name if linked, nothing otherwise.
Workspace routing
/workspaceNavigate between the three kinds of workspace you can be working inside at any moment: your own personal workspace, a collaborator's workspace you've been invited to, or a channel-shared workspace.
Switch to another user's personal workspace (requires collaborator access). Call with no argument to return to your own. Inside an open channel session, this doesn't override the channel-shared workspace.
List every workspace you can reach — your own, workspaces you've been added to as a collaborator, and any open channel sessions in the current server.
Show which of the three workspace states is active right now: your own, a collaborator's, or the channel-shared workspace for this channel.
Wipe every file in your personal workspace and start clean. Your container is kept; only the files inside are cleared. Sessions, memory, and linked GitHub credentials are untouched. Cannot be undone.
Tear down your personal workspace container and rebuild it from scratch — files cleared, container recreated with the latest base image and tooling. Use when something inside the container has gotten into a bad state.
Bring your own tools
/mcpConnect Model Context Protocol servers to your workspace. Their tools surface as Ergod tool calls automatically — no glue code, no per-server slash commands to memorize. Two transports: remote (streamable-HTTP, anything you can reach over the network) and stdio (runs inside your sandbox container; one-click installer handles common launchers like npx and uvx). MCP is on by default for new tenants. Crashed stdio servers are detected and you're prompted to recover.
In a channel session, your personal MCP inventory does not auto-apply to the shared workspace. Each server has to be explicitly granted with /mcp share <name> — otherwise it stays personal. This is deliberate: bearer tokens you registered for personal servers never leak into a shared session you happened to sponsor. Install and Always-Approve prompts in shared sessions only respond to privileged users (sponsor + Discord guild admins + bot admin), so one channel member can't auto-approve servers on everyone's behalf.
Show every MCP server registered to your workspace, transport type, enabled state, and current health.
Connect a remote MCP server over streamable-HTTP. Ergod handshakes, lists the server's tools, and starts surfacing them on your next turn.
Add a stdio MCP server that runs inside your sandbox container. If the launcher (npx, uvx, etc.) isn't installed, Ergod offers a one-click install. Ack and install collapse into the same click.
Probe a registered server and print everything it exposes — tools, resources, prompts. Useful for debugging a server that isn't surfacing what you expect.
Disconnect and forget the server. For stdio servers, also stops the in-container process. Any channel-session grants of this server are revoked at the same time.
Turn MCP on for your workspace. On by default for new tenants — use this if you've previously turned it off.
Turn MCP off across your whole workspace. Registered servers stay configured but no tools are exposed to the model. Re-enable any time with /mcp on.
Re-enable a specific server you'd previously disabled.
Disable a single server without removing its registration. Its tools stop appearing until re-enabled.
Grant one of your own registered MCP servers into the active channel session. Privileged-only (sponsor, Discord guild admins, bot admin). Admins can't share someone else's tokens — only the owner can grant their own server. Idempotent.
Revoke a previously granted server from the channel session. Privileged users or the original granter can revoke. Idempotent.
List the MCP servers currently granted into this channel session — server name, who granted it, and when. Anyone in the channel can run this. The underlying URL, command, args, and headers are never shown by any sharing command — those stay write-only after /mcp add; to change a config you re-add, never read it back.
In your personal /mcp list, each server is annotated with whether it's shared and into which channels — so you can manage your sharing scope from one place.
Collaborators
/collab Pro onlyAdd individual Discord users to your own personal workspace. Each collaborator you add can read and write your files. They use /workspace switch to enter. Different from channel sessions, which open a shared workspace to everyone in a channel. Collaborators never inherit your GitHub push credentials.
Grant one specific Discord user access to your personal workspace.
Revoke an individual's access to your personal workspace. Their stale workspace view is cleared automatically.
Show which individual users currently have access to your personal workspace.
Shared channel workspace
A channel session opens a single shared Ergod workspace that everyone in the channel reads and writes to together. Contrast with /collab, which adds individual users to your own personal workspace. A channel session needs a Pro sponsor: the admin who opens the session nominates a Pro user, who accepts or declines. Sessions renew every 90 days (accept / snooze / don't-ask); if the sponsor drops to free tier, the channel session auto-freezes until a new sponsor accepts. Admins can block users or the whole channel from ever being offered a session again.
Nominate a Pro user to sponsor a shared Ergod session in this channel. They receive an Accept / Decline prompt; the session only activates after they accept. Requires Manage Channels.
Close the channel session. The shared workspace is retained for 90 days in case you re-open, then swept.
Show whether this channel has an open session, who's sponsoring it, when the next renewal prompt fires, and whether the session is currently frozen (sponsor lapsed from Pro).
Block a user from being nominated as a sponsor, or block a whole channel from ever being offered a session. Nominations already sent are cancelled.
Remove an entry from the channel-session blocklist. Idempotent.
Show the current channel-session blocklist for this server — users and channels that can't be involved in a shared session.
For Pro users: list the channel sessions you're sponsoring across any server, with each session's next renewal date. Same command listed under /session — shown here for discoverability.
Server admin
/ergod-config Manage Channels+Server-level controls. Gated on Discord's native Manage Channels permission (or any higher admin role) — no extra Ergod role to set up.
Show Ergod's configuration in this server — channel rules, role blocks, thread mode, mention scrub state, deny-reply mode.
Set whether Ergod creates a thread for each message by default across the whole server.
Override thread mode for the current channel. default clears the override and returns to the server-wide setting.
Allow Ergod only in the given channel (if using an allowlist) or block it from that channel. Stacks: call repeatedly to build a list.
Block or unblock a role from using Ergod in this server. Idempotent — safe to call more than once.
Toggle scrubbing of @everyone, @here, and role pings in Ergod's replies. On by default.
Choose how Ergod tells users they're blocked — an ephemeral reply only they see, or silent (no reply at all).
Join the Discord or add Ergod to your own server. Free tier includes sessions, GitHub linking, and image input — no card required.