Discord AI Agents: What They Moderate and What They Miss

It is one in the morning. An account that joined nine minutes ago has posted the same free-Nitro link in four channels, two people have already clicked it, and you are deleting messages one at a time on your phone. In another tab, someone in #help is asking the question you answered on Tuesday.

Say the server has four thousand members and two moderators. Neither of you is paid for this.

That is the job people are trying to hand over when they search for a Discord AI agent. Not a coding project. The one in the morning part.

I run an AI agent platform, so the version of this I hear most is people asking whether an agent can just watch a server. The honest answer has an order to it. Moderation goes first: high volume, and almost everything the agent does there can be undone with a click. Answering members in public goes second, because a wrong answer in #general does not un-happen.

What is a Discord AI agent?

A Discord AI agent is software you install in your server and give a goal instead of a command list. It reads the channels you allow, decides which steps the goal needs, then takes them or queues them for you. A moderation agent is the common first one.

Where the word bot stops being accurate

Almost everything in your server today is a bot in the strict sense. You filled in a settings screen, and a fixed behaviour now fires when a fixed condition matches. Discord's own AutoMod is the cleanest example: you give it words and patterns to block, it ships presets for spam and the obvious categories, and it applies exactly those rules, fast and free.

That model has one weakness and every community manager has met it. Scammers rephrase. Your filter catches "free nitro" and misses "free nitr0", then misses the version with a zero-width space in it, then misses the screenshot. You spend Sunday adding patterns, permanently one incident behind.

An agent is given the goal instead: keep scam links out of these channels. It reads the message the way a moderator would, in the context of who posted it, when they joined and what else they have posted this hour. New phrasing does not require you to update anything.

The agent is a different unit of instruction. For a bot you write configuration; for an agent you write the brief you would hand a new volunteer moderator, covering what matters, what the edge cases are and what to do when it is unsure. The difference between an agent and a chatbot is the same line drawn in a different room.

What a Discord AI agent actually does

Five jobs come up again and again, and they are not equally safe. Read the last two columns first: what the agent is allowed to finish on its own, and what it should hand back with the context attached.

The split turns on one thing: whether the action can be undone. A deleted spam message and a one hour timeout are reversible in a click; a ban and a wrong public answer are not.

Two of those deserve singling out. Welcome is the one I would switch on first: worst case is an awkward greeting, best case is that your join-to-first-message rate stops being embarrassing. Repeat questions is the one most people want first and should switch on last, because it is the only job here where the agent speaks in public under your server's name.

If your community lives in Slack instead, the same five map across almost unchanged, and the Slack version of this page covers where the platforms differ. The wider catalogue is in what an AI agent can actually do.

What you need before it works

None of this is programming, but somebody has to sit in Discord's developer portal for twenty minutes and make three decisions. Get them wrong and you have either an agent that cannot see anything or one that can see far too much.

The app, the bot user and the token

Every agent that lives in a Discord server does so through an application you register in Discord's developer portal. The application gets a bot user, the bot user gets a token, and that token is the credential your agent signs in with. You then invite it to your server with a specific set of permissions attached.

Treat the token like a password to your server, because that is what it is. It belongs in a secret store, never in a message, a pinned config file or a support thread. If it leaks, regenerate it in the portal and every old copy stops working.

One thing to know before you scale: Discord lets you switch privileged intents on yourself while your app reaches fewer than 10,000 users across every server it sits in. Cross that line and you have to apply for them, with 90 days from Discord's notification to get the application in before access is withdrawn. That is not a concern for one community. It becomes one the day you run the same agent across five large ones.

Intents decide what your agent can read

Discord splits the events an application can subscribe to into ordinary ones and a small set it calls privileged, switched on per application and reviewed at scale. Three matter for community work: message content, server members and presence.

Message content is where people get stuck. Without it your application is told that a message happened, by whom and where, but not what it said, unless the message mentions the agent or arrives in a DM with it. A moderation agent watching a public channel is otherwise reading the envelope and guessing at the letter. Server members covers join and leave events, which is what any welcome job runs on. Presence covers who is online, and you will probably never need it.

Turn on only what the job requires. Each intent widens the volume of member data flowing through a third party, and an agent that never receives presence data can never mishandle it.

Scope the permissions to the channels you actually mean

Discord lets you grant a role permissions across the whole server, then override them channel by channel. Most people grant server-wide because it is one click, and that is the decision that hurts later. Give the agent its own role, then grant that role access on the specific channels the job names.

• View Channels and Read Message History. The floor for anything that reads. Grant them only on monitored channels.
• Send Messages. Only where the agent is meant to speak. A moderation agent that never posts in public needs this in its mod channel and nowhere else.
• Manage Messages. Required to delete anything, and the permission that does real damage server-wide. Worth the extra five minutes of scoping, and limiting what an agent is allowed to do runs the same exercise for tools other than Discord.
• Moderate Members. Discord's timeout permission. Reversible, which makes it the strongest thing I would grant by default.
• Kick Members and Ban Members. I would leave both with the humans.

Six months from now, when somebody asks why the agent can see #staff, the answer should be in a document rather than in someone's memory. Write the list down before anyone clicks anything, and keep it beside the agent's brief.

Where it goes wrong

An agent can be wrong in ways a keyword filter cannot, because a filter misfires predictably and an agent surprises you. Four failures are the ones worth designing against before you switch anything on. Two of them are configuration rather than intelligence.

• Permissions granted at the server level. The agent was set up to watch #general and quietly inherited #staff and the channel where you discuss members. Nothing breaks. You find out later that a third party has been reading your moderator conversations for a month.
• Replying where it should only read. An agent with Send Messages everywhere will eventually answer in a channel your community treats as theirs, and the tone shift gets noticed immediately.
• Rate limits during the wrong minute. Discord limits how fast any application can call its API and asks you to back off when you cross a limit. A raid is when you generate the most actions per second, so ask whoever built your agent a plain question: when Discord tells it to slow down, what happens to everything it has not got to yet?
• The false positive that lands on a real member. A three-year member posts an in-joke that reads as a scam pattern out of context, and gets timed out at midnight with nobody awake to reverse it.

That last one is the only failure here that costs you a person, and it is why I keep arguing for a narrow allowlist: let the agent finish only what a click can undo, and route the rest to a queue. The defence is a log your moderators can read, showing what the agent saw, what it decided and how to reverse it. Monitoring agent activity and the guardrails post cover the general version.

What it costs

Gravity is in private alpha, so the honest framing is what you get when you are let in, not what you can sign up for this afternoon.

Your first agent is free and there is no card. After that Pro is $5 a month during the alpha, and Max is $20 a month for more agents and more usage. It is one USD price list for everyone. If you run through the included usage, buy more from your account. A run that fails on a platform error, with no usable output, is refunded under the refund policy.

I am not going to claim a one-click Discord install you cannot verify today. The honest path is the one everyone in the alpha takes: describe the job when you apply, including the channels and the stop rules, and the agent is built against the permissions you grant it. That makes the scoping work above part of the specification. If you want the comparison in cash terms, the cheapest AI agent platforms prices the alternatives on all-in cost, and the profession hub shows the same pattern outside community work.

Price is rarely the deciding question at community scale anyway. Two unpaid moderators covering four thousand members at one in the morning is a staffing problem with a small software budget attached.

FAQ

Sources