Discord vs Slack for AI agents: one open source agent, two rooms

Audience before app

Who is in the room sets what the agent may reach and say.

An internal room and a public room ask different things of an agent. A Slack workspace usually holds a company's own people: product, support, finance, each with an account and a role. A Discord server usually holds customers, or a community that formed around a product. One sentence from an agent can be ordinary in the first room and expensive in the second. A reply that quotes an open incident, a contract value or an unannounced release is fine among colleagues. In a server with a few thousand members it is a leak.

Reach follows the room. A connector to the CRM belongs in a channel where everyone present is a member of staff. A public server needs a shorter grant list, because anyone in the channel can read what the agent answers, even when only allowed people can start a session.

So settle the audience first: employees, customers, or a community. The app follows from that answer.

One thread, one session, in both apps

The mechanics are closer than the argument suggests. Kortix documents the same shape on both apps: a mention starts a session, and the thread is where the agent answers. In Slack, one thread is one session. In a Slack channel only a mention reaches the agent, so a reply without one stays between people. In Discord, a mention in a text or announcement channel starts a thread on the message, and a later mention in that thread continues the session. A direct message is its own session until /new.

Two Discord details shape a rollout. Threads archive after a day without messages, and a new message opens the thread again. A project also makes at most 60 Discord calls a minute, which sets the ceiling on a busy server.

Teams differs more. Each channel post is its own session, so a conversation spread over three posts is three sessions.

Who the agent thinks is asking

A Slack or Teams message carries no Kortix login. Each person links an account once, with /kortix login in Slack or /login in Teams. The link works once and expires after 10 minutes. After that Kortix checks that the sender is a project member who may start sessions, and the agent still acts with its own permissions, not the sender's role.

Discord has no account link. The allowed-user list decides who may talk to the bot, as on Telegram. A mention or direct message from anyone else gets a reply showing their Discord ID, and the request appears for a project manager to allow or dismiss.

Both designs narrow access, and they record different things. A linked account ties a question to a person and a role. An allowed ID ties it to an account that someone approved. If the team needs to know who asked, to answer well or to explain later, that difference matters more than the chat features do.

Slack adds a join policy for the session itself: Open by default, Approval, or Owner only. Discord's control is the allowed list plus the server the project is bound to, and one project has one server.

What switching apps does not change

The work sits behind the channel. The agent is the same persona with the same skills, and its access starts off: it gets no connector, secret, skill, App or project repository until a person grants it. Connector credentials are brokered server-side and never enter the machine, so a public Discord server and a private Slack channel can reach the same CRM without either room holding the login.

Approvals travel with the session. Approval gates you set. Off until you set them. A request that needs a person stays with the session the thread started, and a project manager, or the person who started it, decides. In Slack and Teams, the card in the thread carries the title, a summary, a risk note and Approve and Deny buttons, plus View in Kortix. In Discord, the Guide documents the buttons on questions, and a held action opens under Approvals in the session header, on Review → Needs you, or through the approval link.

The repo is the constant. Skills, memory, connector grants and approval rules live in the project. Run it on Kortix Cloud, in your VPC, or on your own on-prem network. Self-host is free. A second channel then adds a room to the same agent instead of a second agent.

A short way to decide

• Employees first. Start in Slack or Teams, link accounts, and grant the internal connectors the work needs.
• Customers or a community first. Start in Discord, keep the allowed list short, and grant only what a public thread can bear.
• Both audiences. Connect both channels to one project, so the agent, skills, grants and memory stay one set.
• A busy Discord server. Plan around the 60 calls a minute and threads that archive after a day.
• Any write that needs a person. Decide who approves it and check where they will see the request before the first live call.

A company that runs one bot in Slack and another in Discord ends up with two half-agents: two skill sets, two grant lists, two memories, and no way to carry a question from the customer in Discord to the engineer in Slack who can answer it. Keep the project as the agent and the chat apps as rooms it can enter.