How Onyx builds a Discord server

Most AI server tools generate a layout and hand it over. Onyx works the other way round: it looks at what you already have, proposes a change, and waits.

The five steps

  1. 1

    You describe the server

    In plain English, in the AI Builder on the dashboard. "A Valorant clan server with ranked channels, LFG, and staff-only mod logs" is enough. The more specific you are about who is allowed where, the closer the first pass lands.

  2. 2

    Onyx reads the server you already have

    It looks at your existing channels, roles and permissions first. That is the difference between building for your server and pasting a template over it: an existing structure gets extended, not flattened.

  3. 3

    It writes a plan, and shows it to you

    You get the full plan before anything is created: every channel, every role, every permission, every feature it intends to configure. Nothing has touched Discord at this point.

  4. 4

    You apply it, or you do not

    Applying is a deliberate click. Until then the plan is just a proposal you can argue with, and arguing with it in follow-up messages is the intended way to use it.

  5. 5

    You keep talking to it

    Follow-ups work on what it just built. "Make the LFG channels voice instead", "lock the mod logs to staff". It has the context of the previous turn, so you are refining rather than starting over.

Why the plan step matters

The dangerous part of automating a Discord server is not creating a channel. It is permissions. A channel that was meant to be staff-only and is not is the single most common way a server leaks something it should not have.

Showing the whole plan before it runs is what makes that survivable. You can read the permission overrides for a private channel and confirm they say what you meant, while it is still a proposal. If it is wrong, you say so and it revises. Nothing has been created, so nothing has to be undone.

What it does not do

It does not act on its own. Onyx does not run in the background, does not act on a schedule, and does not change anything you did not apply.

It does not replace moderation judgement. It configures the moderation features. Deciding what your community tolerates is still yours.

It does not guess at your members. It reads server structure, not private message content, when it plans.

Where it lives

The AI Builder is on the PeakBot dashboard, per server. Add PeakBot to a server, open the dashboard, pick the server, and the builder is there. See what it can build and configure for the full list, or the questions and answers for pricing and limits.