Answers from our docs and articlesesc to close
Try asking
Create an accountSign up

Auditor in Slack: ask about your code, hand it the change, and put your automations in a channel

Mention @Auditor in Slack to ask about your code, get a plan or a pull request, run automations, and have them post what shipped to a channel.

Key takeaways

  • Connect your Slack workspace from Auditor › Automations, or add Auditor from Slack and pick your team; a Slack workspace works for one Inference Bureau team.
  • Mention @Auditor, message it, or type /auditor: it answers from the code and its history (merged pull requests, commits, deployments), plans a change, or makes it and opens a pull request, with a line in the thread saying what it's doing until the answer streams in.
  • Run, pause and resume automations by name, or ask for something recurring and press Create on the draft. Automations can post their own message to a channel, and a reply in its thread continues the run.
  • Anyone in the workspace gets answers and plans; members of your team, matched by their Slack email, can have it change code. Model calls are billed to your Auditor key like reviews.

Auditor in Slack is open to every team from today. It's the same Auditor that reviews your pull requests, answers @auditor on a GitHub issue and works on a Linear issue you assign it, now in the place most of the questions about the code get asked in the first place: a channel.

It does two jobs. It's someone to ask, with the repository open in front of it. And it's where your automations can live: started, paused and set up from a message, posting what they found to a channel you pick.

Connecting it

On the Auditor page, open Automations and choose Connect Slack. Slack asks you to allow Auditor in your workspace, and that's it: Auditor is the workspace's app, not yours, and it sends whoever installed it a message saying how to use it. Only owners and admins of your Inference Bureau team can connect Slack, and a Slack workspace works for one team.

You can also start on Slack's side with Add to Slack. Slack's consent screen comes first; then you sign in to Inference Bureau and pick the team the workspace is for. The page names the workspace, so nobody connects one they didn't mean to, and Cancel takes the app back out.

Auditor can post in any public channel. For a private one, invite it first with /invite @Auditor.

Ask it something

Mention @Auditor in a channel, message it directly, or type /auditor and your question. A line shows up in the thread at once and changes as it works: Reading src/payouts/email.ts…, then Searching for "formatAmount"…, then Checking deployments…. When it has the answer, the line goes and the answer streams in as text.

It answers from the code, at the default branch or at a pull request's head, and from the repository's history on GitHub: the pull requests merged since a date, the commits on a branch, one pull request in full, and the latest deployments as Vercel (or any host that reports to GitHub Deployments) recorded them. So the questions that used to mean opening four tabs get an answer with links:

  • What merged this week, and what does it mean for the release?
  • What does #418 change, and is anything in it risky?
  • What was the last production deploy, and the one before it?
  • Where do we retry failed webhooks, and how many times?

Ask for a plan and it writes one: the files and functions it would touch, what it would leave out, how it would test it, and what it needs you to decide. Ask for the change and it makes it, with tests where the repository has them, checks it with the repository's own tools in a sandbox, and opens a pull request. When that pull request's preview deploys, the link appears in the thread.

A thread is one conversation. Reply in it to continue, with the earlier work in place: push back on the plan, then say go ahead. A reply sent while it's still working is read before its next step. Mention it in the middle of someone else's thread and it reads the thread so far first.

It works in the repository your message names (ib/web, or just web when only one repository has that name, or a link to a pull request). Otherwise it uses the channel's repository, which you set with repo owner/name, and with only one repository on your team, that one. When it can't tell, it asks.

Automations from a channel

Three commands cover what you'd otherwise open the Automations page for:

  • list shows your team's automations, when they run and whether they're on.
  • run <name> runs one now and answers in the thread. Anything after a colon goes to the agent: run Weekly summary: only the billing work.
  • pause <name> and resume <name>.

Ask for something recurring in plain words, every Monday at 9, post what shipped here, or when a pull request merges, post what it changed, and Auditor drafts the automation: its trigger, the repositories, what it does each time, and this channel to post to. It shows the draft with Create and Cancel. Nothing is set up until an owner or admin presses Create, and you edit it afterwards like any other automation.

Automations that post to Slack

Any automation can now post to a channel of your connected workspace. The agent writes the message itself, rather than a list of what each run did, and Auditor posts it once per firing, or nothing at all when the agent has nothing to say. The message's thread is the run's conversation: reply to ask why something is on the list, or to have it look closer.

Three new recipes are built for it:

  • Weekly summary of what shipped: Mondays, across your repositories in one run, the week's merged pull requests grouped into features, fixes and internal work, with links and authors.
  • Post each merged pull request: what changed and why it matters, with migrations, new settings and breaking changes called out. A dependency bump with nothing to say posts nothing.
  • Daily digest: what merged and landed since yesterday. Quiet days post nothing.

Two changes under them apply to every automation. A pull request trigger can now fire on a merge, reading the base branch at the merge commit. And every run can read the repository's history, with a schedule knowing when it last fired, so "since last time" means what it says.

Who can do what

Auditor matches the person in Slack to your team by their Slack email address:

  • Anyone in the workspace can ask and get answers and plans.
  • Members of your team can also have it change code, open pull requests and issues, and run automations.
  • Owners and admins can also create, pause and resume automations, and set a channel's repository.

Someone who isn't a member is told so when they ask for more than an answer or a plan.

What it costs, and what it reads

There is no seat price and no fee for the app. Every model call is billed as inference to your team's Auditor key, like a review, under the same spend caps. The conversations are runs of your team's Issue assistant automation, the one that answers on GitHub issues and in Linear, so its budget per reply and per month applies; an automation run from Slack keeps its own. Drafting an automation from a message is one short model call.

Auditor reads the messages that mention it or are sent to it directly, replies in the threads it answers in, the earlier messages of a thread it's mentioned in, and the name and email of whoever wrote to it. It doesn't read other messages or channels. The bot token is stored encrypted, and nothing it reads is used to train models. The privacy policy has the details, and Disconnect on the Slack card deletes the token.

Frequently asked questions

Does everyone in our Slack workspace need an Inference Bureau account?

No. Anyone in the workspace can ask Auditor and get answers and plans. Having it change code or run automations needs a member of your team, matched by the email on their Slack profile.

Can we keep using a Slack incoming webhook for an automation?

Yes. A webhook URL still posts the same digest it did. Picking a channel of the connected workspace instead has the agent write the message, and lets you reply in its thread.

What happens to a long-running change?

The line in the thread keeps saying what it is doing until the answer is ready. However long that takes, the answer arrives in the same thread.

Can one Slack workspace serve two Inference Bureau teams?

No. A Slack workspace works for one team. An owner or admin of that team can disconnect it under Auditor › Automations so another team can connect it.

One bill for your apps, your models and your reviews.

Host apps and functions next to your model traffic. Routing picks each turn's model by your quality floor, and Auditor reviews every pull request against your own rules.