The AI studio builds a server with you. You describe what you want, the AI suggests the channels, roles, permissions and Dispatch.IO module configuration; you fine-tune by talking to it or directly in the preview, then you apply to one or several servers.
It's in the server dashboard, Forge › AI studio. The studio is free for everyone, with a number of uses per day (see Quotas).
The studio screen
- On the left, the conversation with the AI.
- On the right, the preview: the server as it will appear, as in the app (categories, channels with their type icon, coloured roles), enabled modules as cards and a permissions panel.
Everything can be edited by hand in the preview: drag a channel to move it, rename, delete, change a role's colour. The AI sees your changes with your next message.
Generate a server
- Describe your server in a few sentences: the topic, the audience, what happens there. Example: "server for my French Twitch community, 2,000 viewers, clips, Valorant tournaments on Fridays, staff of 6 mods".
- Optionally specify: the target platforms, the community size, the language, the tone (serious, relaxed, fun).
- Click Generate. The AI fills in the preview: categories, channels, roles and permissions, tickets, logs, levels, welcome messages, announcements…
A generation uses 1 generation from your daily quota.
Fine-tune with the assistant
Then talk to the AI like a colleague:
- "add a channel for clips";
- "make tickets stricter";
- "merge the two gaming voice channels";
- "mods must not be able to ban".
Each answer is a change to the preview (additions in green, updates in orange, deletions in red), which you keep or undo in one click. Each message counts towards the assistant quota.
Apply to one or several servers
When you're happy with the preview:
- Click Apply.
- Choose the target servers: the current server, and optionally other servers you manage, on any platform (for example Discord: My Community and Stoat: My Community). This is a project: you can reopen it later from the studio.
- With several targets, Forge offers to link the matching channels (each server's
#general, for example) with linked channels. - Check the list of changes for each server, then apply.
You can also Save as template to keep it in My templates without applying it.
Audit an existing server
The Forge › Audit tab has the AI review your server: its structure, permissions and Dispatch.IO configuration (never messages). The report ranks what it finds:
| Level | Examples |
|---|---|
| Critical | @everyone can mention everyone; the log channel is visible to all; a moderation role has Administrator. |
| Recommended | Anti-raid is disabled; two roles have exactly the same permissions; no rules channel. |
| Idea | A suggestions channel, level roles, a warmer welcome message. |
Each item has a Fix button: it opens the list of changes with the fix, to check then apply. An audit uses 1 audit from your daily quota. From Discord: /forge audit.
Write the texts
The Write with AI button appears in the studio and next to Forge texts: rules, welcome and goodbye messages, embeds, channel descriptions, ticket texts. Choose the tone and language, proofread, edit if needed, then keep the text. Each text uses 1 writing from your quota.
Quotas
Quotas are per Dispatch.IO account, not per server, and reset every day at midnight, Paris time.
| Per account and per day | Free | Basic | Ultimate |
|---|---|---|---|
| Full generation | 3 | 10 | 25 |
| Messages to the assistant | 20 | 60 | 150 |
| Server audit | 1 | 5 | 15 |
| Writing | 10 | 40 | 100 |
The remaining count is shown next to each button ("2/3 generations today"), in Personal space › Forge and with /forge quota. A failed generation doesn't count.
Note
If the AI service is under heavy load, the studio may be paused for everyone until the next day. The rest of Forge (Vault, templates) keeps working.
What is sent to the AI
The studio uses Gemini (Google). It only receives what it needs:
| Sent | Never sent |
|---|---|
| Your description and your messages to the studio | The server's messages |
| The structure of the server or the preview (channel and role names, permissions) | Members (usernames, assigned roles, XP, sanctions) |
| The Dispatch.IO module configuration | Keys, tokens and payment data |
Everything the AI suggests goes through the same safety rules as a template: it can never grant Administrator or a management permission to @everyone, and nothing is applied before you've seen the list of changes.
Depending on the platform
The studio suggests everything Discord allows: forums, announcement and stage channels, stickers, module buttons.
The studio adapts its suggestion to Fluxer: module buttons become reactions and forms on the website, as everywhere on Fluxer (see Buttons, forms and replies on Fluxer). From the bot: d!forge audit.
The studio only suggests text and voice channels, no stickers, and channel permissions per role. Module buttons become reactions and forms on the website. From the bot: d!forge audit.
Related pages
- Restore and apply: what happens when you apply.
- Templates: start from a model rather than from scratch.
- Linked channels: chat between a project's servers.