Discord

How Discord Works Here

Members reach the bot with a slash command, not by chatting normally. Typing /ask how much is shipping? gets an answer; typing how much is shipping? in the channel does not.

That is on purpose. A bot that reads every message in a server needs far broader access to your community's conversations, and it would spend your credits on chatter it was never asked to join. The slash command keeps the rest of your server private and puts your members in control of when the bot is listening.

Add to Server (one click)

Open Configurations → Channels in the dashboard sidebar, and on the Discord card choose Authorize. The dialog opens with Add the ProxyAI bot to your server and its Add to Server button.

1. Choose Add to Server. Discord's permission screen opens in a new tab.
2. Pick the server. You need the Manage Server permission on it, Discord's rule for adding any app, not ours.
3. Choose Authorize. You come back to your ProxyAI dashboard.

Members can then use /ask in that server. Nothing to create, nothing to configure, no developer site to visit.

The bot asks for two permissions: View Channels and Send Messages. The slash command works without either, they are what let a human on your team reply into the channel from the ProxyAI inbox.

To add a second server, choose Add to Server again and pick it. To remove the bot, remove it from the server in Discord.

One quirk worth knowing: the card's Recheck menu item only looks at the Advanced settings below, so after a one-click install it says "Not configured". The connection is fine, confirm it by running /ask in your server.

Advanced: Use Your Own Bot

Choose this when you want the bot to carry your own name and picture, a command other than ask, or to answer direct messages. It means creating an application on Discord's developer site, so it is a step up in effort.

1. Open the Discord Developer Portal and choose New Application. The name you give it is what members see.
2. Open the Bot tab, choose Reset Token, and copy the Bot Token. Discord shows it once.
3. Open General Information and copy the Public Key. ProxyAI uses it to confirm requests really come from Discord.
4. In the ProxyAI dialog, below Advanced, bring your own bot, paste both.
5. Optionally set a Slash Command name, lowercase, no spaces. Leave it blank for ask.
6. Choose Save.

The dialog also shows an Interactions endpoint URL with a copy button. You do not need it: saving checks your bot, creates the slash command and points your application at ProxyAI for you.

Then invite your bot:

1. Developer Portal → Installation.
2. Under Installation Contexts, enable Guild Install for servers, and User Install too if you want the bot to answer direct messages.
3. Under Default Install Settings, give it the applications.commands and bot scopes and the Send Messages permission.
4. Copy the Install Link, open it, and pick your server.

Both values are secrets. If either gets out, reset the token on Discord's site and save the new one here.

Test It

In a server where the bot is installed, type /ask and send a question. Discord shows the bot thinking, then the answer arrives a few seconds later.

• The command does not appear, a brand-new command can take up to an hour to reach every server, and Discord caches the list per device. Wait, then reload with Ctrl+R (Cmd+R on Mac). Check the bot was invited with the applications.commands scope.
• "This server is not connected to an assistant yet", the bot is in the server, but no ProxyAI bot has claimed it. Run Add to Server from your dashboard.
• "This assistant works inside a server", you messaged the shared ProxyAI bot privately. The shared bot answers inside servers only; direct messages need your own bot with User Install enabled.
• "The application did not respond", the answer took too long, or the connection was refused. On the Advanced route, save the Discord settings again.
• Saving fails with an invalid-token error, the token was reset after you copied it. Reset it once more and paste the fresh value.
• A human reply never arrives, the bot lacks Send Messages in that particular channel. Check that channel's own permissions, not just the server-wide role.

Conversations and Privacy

In the agent inbox a conversation belongs to a Discord channel, not to one member. In a shared channel everyone using the command there shares one history, and a human reply is visible to the whole channel. Direct messages, where you have enabled them, stay private to each member.

The bot only ever sees the text typed into the command. Everything else said in your server stays out of ProxyAI.