Discord integration

AI agents in Discord, without the context switching

Mention @Nairi in any Discord channel or thread. An AI agent picks up the task, runs against your codebase or runbooks, and replies in-thread. Built on Claude Code, Codex, or OpenCode.

A few things teams use Nairi for in Discord

These are starting points, not the limit. The agent runs whatever you mention it on, with whatever tools you've connected.

Ship code from a thread

Drop a Linear ticket or bug description in a thread. Nairi checks out the repo, makes the changes, runs the tests, and posts a PR link in the same thread.

Run on-call playbooks

Page Nairi from your on-call channel. It pulls logs, checks dashboards via MCP tools you configure, and correlates with recent deploys.

Triage support

Summarize the last 20 messages from a customer-success channel, draft replies, or escalate the ones that need a human.

Schedule recurring jobs

Have Nairi post a weekly PR digest or a daily incident summary at a time you pick. The output lives in your team channel, not in someone’s personal Notion.

Loop the agent into existing threads

Mention @Nairi mid-conversation and it reads the full thread before responding. No re-explaining context.

+ whatever else your team does

Hand it your build script, your migrations runner, your custom CLI, the SQL helper you wrote last quarter. The agent uses what you give it.

Your Discord agent with your stack

Conversations from Discord route to an agent in your org. Configure what the agent can reach: repos, MCP servers, skills, secrets, custom rules. Add or remove any of these any time.

Where you talk to the agent
Discord
Mention @Nairi in any channel, thread, or DM
Nairi agent
Isolated container, one per agent, inside your org
Claude CodeCodexOpenCodeCursor
What the agent can reach
GitHub repos
Read code, open PRs, run CI
MCP servers
1,000+ including Postgres, Linear, Notion
Skills
Reusable prompts and playbooks
Vaults
Secrets injected at runtime
Rules
Custom instructions per agent

Common workflows

A few of the patterns teams reach for on day one. The agent does much more than this once you wire it into your stack.

01

PR review and code shipping

Engineers mention Nairi with a ticket link or bug description. It checks out the repo, makes the changes, runs the tests, and opens a PR with a summary in the thread. Reviewers respond inline. Nairi keeps full thread context, so follow-ups don’t need re-explaining.

02

On-call incident response

Page Nairi from your on-call channel during an incident. It pulls logs, checks dashboards via MCP tools you configure, correlates with recent deploys, and posts findings in the thread. The full investigation stays as a thread, ready for the postmortem.

03

Async product and eng updates

Schedule Nairi to post a recurring update: last week’s shipped PRs, open incidents, customer escalations. No one has to remember to write it. The update lives in your team channel, not in a doc nobody reads.

How it works

Install in 30 seconds, then choose what to connect. Your secrets stay in your vault, injected at runtime via a secret proxy. The chat surface never sees them in plaintext.

  1. 1

    Add the Nairi bot to your Discord server

    One-click OAuth, around 30 seconds. You pick which channels Nairi can see and which roles can invoke it.

  2. 2

    Connect what the agent should reach

    Pick from GitHub repos, MCP servers (1,000+ available, including Postgres, Linear, Notion, or your internal APIs), reusable skills, custom rules, and vault-backed secrets. Add or remove any of these any time.

  3. 3

    Mention @Nairi in any channel, thread, or DM

    Nairi spins up an isolated agent container, runs the task with Claude Code, Codex, or OpenCode (you choose), and replies in-thread.

  4. 4

    The conversation persists

    Follow up, redirect, or ask for changes. The agent remembers the full thread context.

Get started in two minutes

Sign up, add the bot to your server, pick your channels, and mention @Nairi. No infra to deploy. No keys to rotate. No agents to babysit.

Questions about Discord

The things teams actually ask before installing.

No. During install you pick exactly which channels Nairi can see. You can change this any time from your server settings or by reinstalling the bot.
No. Nairi only acts when it’s directly mentioned in a channel or thread, or triggered by a scheduled job you configured. It doesn’t crawl channels, doesn’t initiate DMs, and doesn’t take action without an explicit trigger.
Both. Nairi keeps full thread context, so you can mention it mid-thread and it picks up where the conversation left off. Replies post in-thread by default.
You choose: Claude (Sonnet 4.6, Opus 4.7), GPT-5 via Codex, or open-weights via OpenCode. Configuration is per agent or per channel.
Secrets live in your Nairi vault, never in chat. At runtime a secret proxy intercepts outbound HTTPS calls from the agent and injects credentials only when an authorized agent requests them. Discord never sees them.
Yes. Agent containers can run on your own servers via the open-source nairid daemon. The backend remains hosted by Nairi, so you don’t manage the orchestration layer.
Yes. The Scheduled Jobs feature runs prompts on a cron expression. The result posts to a channel you specify. Common uses: daily digests, weekly reports, periodic health checks.
Discord is included on every plan. See the pricing page for current tiers.