# Open source Discord agent, with company tools and a person's approval

> A Discord AI agent is usually a bot that answers in one channel. Kortix puts an agent in your server that uses the company's own tools, stops at the approval gate you set in Kortix, keeps the answer in the thread and records every action in the session. The code is open source.

URL: https://agentsindiscord.com/

For teams that already live in Discord

**The open-source CompanyOS**

`Kortix Connectors page with the Approval rules panel open: the header "Approval rules — Approval rules that apply to every connector in this project", the two default-behaviour cards "Ask before risky actions" and "Run everything", and the toast "You decide per tool: Allow it, Ask a person first, or Block it."`

```
Your rules decide what each agent may do with each app. An action can **Allow**, **Ask** for a person's approval, or **Block**. Approvals wait on the **Review** page.
```

Source: https://kortix.com/docs/guide#connectors

Approval gates you set. Off until you set them.

[Try Kortix](https://kortix.com) · [See it in a thread](https://agentsindiscord.com/#use-cases)

Open source · Self-host, VPC or on-prem · Discord, Slack, Teams and Telegram channels

## Three jobs a Discord thread can carry

The thread is the conversation; the work happens on the agent's own cloud computer inside the company's project.

### Release notes: Answers what changed in the release

Someone asks in the channel, and the agent reads the project's changelog and commits, then replies in the thread with the lines that matter.

Handed back: `release-notes.md`

| Change | Area | Status |
| --- | --- | --- |
| Retry limit raised to five | Billing worker | Shipped |
| Export CSV added to reports | Reporting | Shipped |
| Webhook signing moved to v2 | Platform | In review |

3 changes in the release

### Incident triage: Triages the alert and hands it to a person

The agent pulls the alert, the last deploy and the affected service from the company's tools, then asks which runbook to run.

Handed back: `incident-brief.md`

- Service: checkout-api
- Error rate: 4.2% over 10 min
- Last deploy: 2 h ago
- Runbook: needs a decision

Waiting on a person

### Support reply: Drafts the reply, and the send waits on a gate you set

The agent looks up the account in the support tool and writes the answer; the draft lands in the thread, and the send waits on the gate you set, which opens in Kortix under Approvals in the session header or on Review → Needs you.

Handed back: `support-reply.md`

- Account: Northwind
- Plan: Team
- Last invoice: paid
- Reply: drafted in the thread
- Send: waits on approval in Kortix

Draft in the thread, decision in Kortix

## The repo is the company

Everything the company runs on sits in one git repo you own.

**The repo.** Open source. Read it, fork it, audit it. Agents, skills, connectors and company memory are files in it, so a change is a diff you can read.

**The model.** A project is that repo, and [one Discord thread is one session](/discord-vs-slack-for-ai-agents) against it.

**The copy.** [Read the source](https://github.com/kortix-ai/CompanyOS).

## How the options compare

Prices and features as each product's own page states them, checked November 2026.

| | Kortix (recommended) | Mava | Beam.ai | AgentX | Discord-AI-Agent |
| --- | --- | --- | --- | --- | --- |
| What it is | Agents, skills, company memory and connectors in one git repo you own. | Support inbox with AI replies for customer conversations. | Catalogue entry for an AI Agent integration on Discord. | No-code agent builder; deploy an agent to a server. | Small Discord bot for AI chat over MCP, run yourself. |
| Where it runs | Kortix Cloud, your VPC, or your own on-prem network. | Mava's cloud. | Beam's cloud. | AgentX's cloud. | Your own machine; you run the bot. |
| Who it can reach | 3,000+ apps, plus MCP, OpenAPI, Postman, GraphQL and raw HTTP. | Support conversations on its channels, not your repos. | Records and operations in the workflows you build. | The agent's own tools inside AgentX. | MCP servers you add to its config file. |
| Open source | Yes. | No. | No. | No. | Yes. |
| Price shape | Free $0, then credits from $50 a month. | Free, then $39 to $599 a month by request volume. | No public price; request access. | Free to start; paid plans on its pricing page. | Installed from source; you host it. |

## Questions people ask about Discord and agents

### How does a held action reach a person from a Discord thread?

The held action stays with the session the thread started. It opens under Approvals in the session header or on Review → Needs you, and a project manager, or the person who started the session, decides.

### Who may talk to the bot?

Only people on the project's allowed list. A mention or direct message from anyone else gets a reply showing their Discord ID and an access request a project manager can approve or dismiss.

### What can the agent reach?

Only what the project grants it. Grants start empty, so an agent reaches no connector, secret, skill, App or repository until a person allows it, and each granted connector is called through Kortix, which holds the login.

### What does self-hosting change?

Your server runs the web app, the API, the LLM gateway and the database. Sessions and Drive still run on Platinum sandboxes that call back to your instance, so the machine holding the Discord connection is yours and the work happens elsewhere.

## Put an agent in the server your team already uses

Start free, add the Discord app from Project admin, and choose the people who may talk to it.

[Try Kortix](https://kortix.com) · [Set up company tools](https://agentsindiscord.com/discord-agent-with-company-tools)

Open source · Self-host, VPC or on-prem · Discord, Slack, Teams and Telegram channels