Slack integration
AI agents in Slack, without the context switching
Mention @Nairi in any Slack 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 Slack
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 Slack agent with your stack
Conversations from Slack 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.
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
Install the Nairi Slack app
One-click OAuth, around 30 seconds. You pick which channels Nairi can see during install.
- 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
Mention @Nairi in any channel 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
The conversation persists
Follow up, redirect, or ask for changes. The agent remembers the full thread context.
Get started in two minutes
Sign up, click "Add to Slack", pick your channels, and mention @Nairi. No infra to deploy. No keys to rotate. No agents to babysit.
Questions about Slack
The things teams actually ask before installing.