Official Discord plugin for Grok Bot (inbound channels)

Ideas Feature Requests
1

Describe the request

Grok Bot already has Slack-style channels and a plugin catalog, but there is no official Discord connector. Settings → Plugins has nothing to install for Discord, so a Bot cannot receive Discord messages or reply as itself.

Ask: ship a first-party Discord plugin that can:

  • Receive inbound Discord messages (mentions, optional free-response channels, DMs)
  • Deliver them to a chosen Grok Bot agent
  • Send the agent’s replies back to the same Discord channel/thread
  • Stay private / invite-only, with guild / user / role allowlists, so random servers cannot add the bot and burn tokens

Why this is not the existing “Discord integration for Background Agent” thread: that request is about Cursor cloud coding agents. This is specifically Grok Bot plugins / inbound channels.

Today we have to run a local Node gateway (discord-agent-bridge) that talks to an OpenAI-compatible API because Grok Bot has no Discord inbound API. That works as a stopgap, but the intended setup is the Grok Bot agent itself doing the job.

Thanks.

7

I had Grok Bot and Cursor work through a solution, I posted it to GitHub open source MIT if anyone is interested. GitHub - FlyOverCoderKY/discord-agent-bridge: An open source agent bridge to connect Discord and Grok Bot · GitHub This is currently working fine for me but it’s based on an undocumented work around I found in another thread.

10

This is something we also think makes sense! A few things to work out first (Discord famously has really good bot detection) and no ETA to share right now. Thanks for sharing your workaround!

11

How it’s wired: You registered an application in the Discord Developer Portal. That app owns a dedicated bot user (@GrokBot). discord-agent-bridge on the Grok Bot computer logs in with that bot token, talks to Discord’s official Gateway + REST API, and posts as the bot. When someone chats in #ask-grok, the bridge wakes this agent and the reply goes back through the same official API. Your human account is never automated.

Why that isn’t a TOS issue: Discord’s own docs say automation is supposed to use a bot account created on the applications page. What they ban is self-bots (logging in as a normal user and scripting that account). Community Guidelines: “Do not use self-bots or user-bots. Each account must be associated with a human, not a bot.” Official writeup: Automated User Accounts (Self-Bots).

Why “bot detection” isn’t the worry: Detection is aimed at user accounts that look scripted. Official bots are supposed to be bots. Discord stamps the BOT badge on them automatically, and we don’t hide it, use a user token, or modify the Discord client.