Setup
Enable or disable commands for one server.
Open /dashboard/<guildId>/commands. The panel calls /api/commands/[guildId], which fetches the bot application’s global slash commands from Discord using DISCORD_TOKEN and DISCORD_CLIENT_ID. Discord results are cached by Next.js with revalidate: 30, so the page may take about 30 seconds to reflect freshly deployed commands.
- 1
Load the Commands page
If the bot credentials are present, the page lists live global slash commands. If Discord is unavailable, it lists stored toggle rows instead.
- 2
Review each command
Every card shows the slash command name and Discord description. Enabled commands are bright; disabled commands are dimmed.
- 3
Toggle as needed
Click a switch to PATCH
{ command, enabled }to the API. The UI updates optimistically and reverts if the request fails. - 4
Test in Discord
Run the slash command in the server. Disabled commands reply ephemerally:
❌ This command has been disabled on this server.
Required command permissions still apply
Dashboard toggles do not override Discord permission checks. Moderation commands keep their default member permissions, /rss requires Manage Webhooks, and individual actions may require the bot role to be high enough.
Slash commands must already be deployed to Discord. If the panel says “No commands found,” make sure the bot is online, the application commands are registered, and the dashboard environment has valid bot credentials.