Quick setup

This page walks you from zero to a configured kesarAI in about ten minutes. By the end you'll have invited the bot, finished the /quicksetupwizard, and confirmed it's responding to commands.

Before you start

You need two things in your Discord server before kesarAI can be useful:

• Administrator permission on your own account — the setup wizard checks for it.
• A moderator rolealready created. If you don't have one yet, create it now — even an empty role works. The wizard will ask you to point at it in Step 1.

You do not need to pre-create log channels./quicksetup can auto-create them if you want.

Invite the bot

Use the “Add to Discord” button at the top of every page on this site and pick the server you want kesarAI in. Approve the requested permissions — kesarAI asks for what it needs to moderate, send messages, manage channels, and read history.

Tip.If you're evaluating the bot first, drop it in a private staging server. Every feature is per-guild, so a test run won't leak any data into your main community.

Run /quicksetup

Once the bot is in your server, run /quicksetup in any channel it can see. The command launches an interactive, eight-step wizard that asks for the configuration most servers want, then writes everything to the config database in one shot.

Step 1 — Mod roles            (RoleSelect, required)
Step 2 — Logs                  (auto-create both / pick existing / skip)
Step 3 — AI access             (Everyone / Roles / Admins-only)
Step 4 — Autopilot             (enable + log channel / skip)
Step 5 — Verify tickets        (member + swap roles / skip)
Step 6 — Quarantine tickets    (quarantine + swap roles / skip)
Step 7 — Welcome               (enable with default preset / skip)
Step 8 — Review + Save         (confirm, then write)

Steps 4 – 7 are skippable: if you don't want autopilot, tickets, or welcome messages, click skip and the wizard moves on. If your server is already configured, /quicksetup first asks whether you want to re-run before clobbering anything.

The setup hub

Run /setupto open the central configuration hub. It's an interactive panel that lists every configurable category and links out to each one's native-select editor — no typing IDs in chat. The hub picks up its sections from a registry, so what you see depends on which cogs are loaded; the typical shipping set is:

• AI access — who can run /ask, /ai think, /ai summarise, /ai fallacy.
• Moderation — assign mod-role permissions (Standard / AI / mod_ai / perm_role / roleban) in a button grid.
• Logs — audit categories, mirror channels, retention.
• Tickets — verify and quarantine flows, transcripts, delayed-delete behaviour.
• Automod — ten rule-based filters (word bans, character checks, flood, invites, links, mentions, dupes) with escalation, per-user overrides, and bypass roles. See the Automod guide.
• Antinuke + Autopilot — guild raid protection and real-time AI message moderation.
• Welcome, Leveling, Game settings, Economy, Casino — opt-in community features.

Verify installation

The fastest smoke test is to run an open command and check it responds. Try /userinfo on yourself:

/userinfo user:@you
✓ Profile card returned.

Then trigger a moderation event and confirm it shows up in the log channel you configured during /quicksetup. If nothing arrives, double-check that the bot has Send Messages and Embed Links permission in that channel — those are the two most commonly missed.

Next steps

The bot is now running with sane defaults. From here, the two most useful pages are:

• Permission tiers — give your mods access to the right commands without handing them the keys to everything.
• AI quota — understand the point budget that gates /ask, /ai think, /imagine, and friends.