Skip to main content
A custom instance is mira running under your bot application. Same commands, same features — different name, avatar, and presence. Members see your bot in the member list, and it’s your token, so you own the application.

​
Setting it up

1

Create a Discord application

Go to the Discord Developer Portal, create an application, add a bot user, and copy the token.Turn on all three privileged gateway intents — Presence, Server Members and Message Content. Without them, most of the bot won’t work.
2

Submit the token

Opens a private form. The token is never typed in chat, so it can’t leak in a screenshot or be sniped from message history.
Your bot will leave every server you don’t own or administrate. A custom instance is only permitted in servers where its owner is the server owner or has Administrator, and it enforces that the moment it connects.This is permanent — it won’t rejoin, and anyone who wants it back has to re-invite it. If your bot is already in servers you’d rather it stayed in, don’t submit that token; make a fresh application instead.The setup prompt asks you to confirm this before the token form opens, and there’s a Cancel button if you’d rather not.
3

Invite it

Generates an invite link scoped to your server.
Aliases for the group: cb, custombot.
Regenerate the token in the Developer Portal the moment you suspect it’s been exposed, then run !instance set again with the new one. A leaked bot token gives anyone full control of the bot account.

​
Customising it

Username changes are global — the bot is renamed everywhere it’s in. Avatar, banner and bio can be set per server, so one instance can look different in each. !instance clear removes the presence. !instance info shows the current configuration.

​
Startup

Connecting happens in two stages, and the setup message shows both:
  1. Connecting — the gateway handshake. If this fails, the token is genuinely bad or the application has no bot user.
  2. Leaving servers you don’t administrate — the access sweep.
If your bot was already in a lot of servers, the second stage takes a while — Discord rate-limits how fast a bot can leave. The instance is already online and usable during this; the setup message reports success and tells you how many servers it left, with the rest finishing in the background.
The sweep also re-runs every 15 minutes. If you lose Administrator in a server, the instance leaves it on the next pass rather than lingering.

​
Removing it

Stops the client and removes the configuration. Your Discord application still exists — delete it in the Developer Portal if you’re done with it. Aliases: disable, delete.

​
Instance vs. customize vs. reskin

Three ways to change how the bot looks, at different levels: customize is free and instant. instance is a real, separate bot that appears in the member list under its own name.
A custom instance runs the same code as the main bot, so it gets every feature and every update automatically. Your server’s configuration — prefixes, welcome messages, tickets, everything — is shared between them.

​
Command reference