Navigation
ELOWEN · Documentation

Last updated: October 27, 2026

Browse documentation · Connect the Discord bot
Channels and chatbots

Connect the Discord bot

Create a Discord bot, invite it to your server, enter its token and choose where it may respond.

Create and invite the bot

  1. Open the Discord Developer Portal and create an application.
  2. Add a bot to it and copy the bot token.
  3. Under Privileged Gateway Intents, enable Message Content. Enable Server Members as well if the bot should list server members.
  4. Invite the bot to your server with permission to read and send messages and to use application commands. Add the Discord permissions it needs for the actions you want it to perform.

Connect it to Chetty

  1. Open Settings → Available plugins and install Discord.
  2. Enter the bot token in Settings → Access → Discord.
  3. Add at least one role policy. See Choose which Discord roles the bot answers.
  4. Enable the plugin. It connects on the restart that saving those settings requests; some settings and per-channel overrides then apply live.

Without a token the plugin does not connect and its tools stay unavailable. The token is stored as a secret, so the setting shows only whether one is set.

The plugin requires Chetty 0.30.47 with shared API version 16.

Connection settings

Setting What it does
Bot token Required secret from the Discord Developer Portal.
Guild ID Optional server restriction and default server for server tools. Empty allows every server the bot belongs to.
Allowed threads Optional allowlist of thread IDs. Empty adds no thread restriction.
Notification destination Channel or thread for proactive messages such as scheduled results. Empty turns them off.
Role policies Maps Discord role IDs to access and room instructions. See Choose which Discord roles the bot answers.

The notification picker needs both the bot token and a server ID; without them it shows no destinations. It lists text channels and active threads, not categories, voice, news, stage, forum or media channels. A channel created in Discord can take up to a minute to appear.

Commands

The bot registers these commands with Discord:

  • /model, /reasoning, /display, /new and /help.
  • The shared commands the daemon publishes, such as /context, /compact, /fast, /stop, /stats and /restart.

/display changes the channel's presentation and requires an operator role. The shared pickers and room controls need one too. See Choose which Discord roles the bot answers.

If the bot stays quiet

  • No commands appear. The token is missing or wrong, so the plugin never connected. Check Settings → Access → Discord.
  • Commands appear but nothing answers. No role policy matches the member, or the member has no linked Chetty account. See Choose which Discord roles the bot answers.
  • The bot ignores a channel or thread. Check Guild ID and Allowed threads. Direct messages and group DMs are always ignored.
  • The notification picker is empty. Set the bot token and a server ID first.