From an idea to
something you can use.

Ask in ordinary words.

In Discord, mention Ergod with your request. In the browser, open Work and type in the conversation. You can attach a file for Ergod to use.

Say what you need, who will use it, and any details that must be right. For work based on your data, attach the source and ask Ergod to check the result against it.

While it works, the live status can show that Ergod is waiting for a model response, receiving it, preparing a tool’s inputs or retrying a request. Preparing inputs comes before the tool runs. These updates describe the current stage, not how much time is left.

Walk through your first request →

Open it. Try it. Ask for a change.

1. Open the delivered file or Ergod link. For an interactive page, use Open full page when you want more room. The creation’s controls run inside the page.
2. Check the part that matters. Try the game controls, check a dashboard total, or read the invitation details. A preview is a quick look at the result.
3. Continue in the same conversation. Name the change and anything you want preserved. Ask for a separate version when you need to keep the original.
4. Or take the step it offers. In Discord, an answer usually ends by naming one next change, and that sentence arrives as a button under the reply. One press sends it as your own message and Ergod does it; typing something else is just as good. In a shared room anyone can press it; on your own work, only you.
5. Keep a copy. Download the file, or use Save a copy to my workspace when the link offers it. A copy becomes your own starting point.

Ergod can open a page it made and try the controls you name. Say which ones matter and anything it must not do. A check covers what you asked it to try, not the whole page, so read the report against what you needed.

For presentations, documents and spreadsheets

Ergod can load a reusable workflow for creating or revising an editable PowerPoint, Word document or Excel workbook. Attach your source, template or existing file, and name what should change and what should stay. The workflows guide it to reuse earlier work, check the final file and send you the editable result.

The checks available depend on the tools in the workspace. A file that opens can still have layout problems, and spreadsheet formulas may need recalculation. Ask what was checked and what remains unverified before relying on the result.

A public share is a snapshot. Editing a workspace file does not silently rewrite that published snapshot. Ask for the updated result and use its new link when sharing the revision.

Find existing work in the dashboard’s file browser or with /files. Return to the original conversation when its context matters.

A link shares a snapshot. The gallery adds discovery.

From a shared creation’s Creation actions, the room sponsor can choose Create public link. It makes an unlisted snapshot that anyone with the link can open without signing in. It does not copy the creation into a personal workspace, and the original shared workspace stays limited to authorized room members.

The snapshot stays separate from the public gallery until you choose Submit to gallery and that exact version is reviewed. You can switch off a public link from Shares.

Gallery cards use the title, description, and preview attached to that submitted version. Editing the workspace file does not change the listing. Replacing, hiding, or revoking the public snapshot removes it rather than silently publishing a newer version.

Your work, or the room’s work.

Just me uses your own agent history, memory, and workspace. If you ask in a Discord channel, the reply remains visible there. The choice describes which work Ergod uses.

Shared room uses the channel’s shared work so people can contribute to the same project. Name the creation you are changing, especially when the room has several things in progress.

On the browser’s Work page, the compact header shows the workspace, audience and your role. Use Sessions for your conversations and Rooms for shared work. Personal conversations and web rooms keep separate drafts. A game opened from a web room includes a named return to that room.

For your own view, Settings → Appearance offers Plum, Rose, Sand and Graphite. Preview a palette, then save it to your account. This changes your dashboard’s colors, independently of the room’s identity or public profile.

Invite someone to the same work.

1. Open a web room in Rooms. Choose Invite someone, then Copy invitation. The invitation includes the dashboard link, a single-use code, and instructions. It expires in a day.
2. Your guest signs in and joins. Under Start or join a web room, they enter the code. Joining opens that room’s shared work.
3. Continue the same board. In Apps in this room, choose Open board beside its name. After making a change, the board’s room link returns to that exact board in the room.

A server admin with Discord’s Manage Channels permission can use a creation’s Manage channel action to open that channel’s existing controls, including the reviewed host-takeover flow when it is available.

Use a direct conversation for private requests. Share files, skills, or connected tools deliberately; a public creation link can be opened by anyone who receives it.

Use the Activity in a voice channel → · Shared-session commands →

Preferences to remember. Procedures to reuse.

Memory holds useful context, such as a preference or project fact. Tell Ergod what to remember, correct, or forget. Skills are reusable instructions for how to do a kind of work.

In Settings → Memory, search your personal notes and choose Open on a result to read it and inspect its available source details. You can correct or forget the note there. If another change was saved while you were editing, compare the latest note with your draft before trying again. Notes too large for the editor stay intact and show an explanation.

Personal and shared work have different scopes. Check which workspace you are using before saving guidance for a group. Use skill commands to inspect and manage reusable instructions.

When a workflow is worth repeating, ask Ergod to save it as a skill. In a personal conversation, for example: “Save our monthly report procedure as a personal skill. Keep the template and recurring checks, and leave out this month’s figures.” Skills are available to load when needed. A one-time revision does not automatically become a saved procedure; check the saved skill and keep any template files it needs.

When you return, name the project and the next change. Files preserve the work; clear follow-ups help Ergod find the right starting point.

Commands manage Ergod. Conversation does the work.

You can ask Ergod to build, explain, or revise something without learning slash commands. Use commands when you want a specific setting or action.

The command reference includes arguments and marks commands supported by the browser composer. Discord’s command picker shows the options available in your current context.

Scheduled tasks have controls in the dashboard’s Settings page. Give a task a name and instructions, choose a repeat schedule and time zone, then save it. You can edit, pause, resume or remove your tasks there. New tasks created in the dashboard currently require a Discord account, run in your personal workspace and deliver to your Discord DM. Scheduled runs use your normal allowance and run no more often than every 15 minutes.

Extra usage when you need it.

A quick question and a large build use different amounts. Check the dashboard or /usage for your current allowance and credits.

Buy a top-up or manage your plan on the dashboard’s Usage & billing page (Account keeps your profile and sign-in methods). After changing your usage, return to the conversation you were working in. Compare all plan benefits →

Connect the accounts your work needs.

MCP is a standard that lets an agent use tools from another service. Ergod can connect to MCP servers, and other agents can connect to Ergod.

Bring your own key means using a supported model provider’s API key with Ergod. The provider bills its model usage separately; Ergod still supplies the workspace and tools. Use the account’s key setup controls rather than putting a key in a shared conversation.

For exact commands and supported connections, see provider-key controls, GitHub linking, and MCP controls.

Give it the source and the question.

Research works best when Ergod knows what you are trying to decide. Name the question, hand it the source when you have one (a link, a file, a pasted passage), and say what must be right. It reads long pages and wiki articles with their headings and tables kept together, and says so when a site cannot be read rather than guessing.

Ask the next question in the same conversation. A follow-up about a different detail can reuse what Ergod already gathered and focus on the part you need: an exception, the passage behind a claim, a figure from the same source. It does not have to start the search again while that material is still available.

Name the requirements when you compare. Ergod can compare documents against criteria you set, keep the comparison, and let you return to the supporting passages. Ask what is supported, what is conditional, where the sources disagree, and what none of them answers.

Work through a list the same way. A list of feedback, tasks or records can be assessed against your criteria, kept, filtered and revisited one item at a time, with unfinished items told apart from assessed ones. When the list changes, ask for a refresh and only the changed items are new work.

Check the conclusions that matter against the passages Ergod shows you. Some sites are unavailable or need a sign-in, and an analysis is a starting point, not a verdict. While it works, you can keep talking: a message sent mid-task is taken as an update to that task (September 17 update).