Auditor in Slack
Mention @Auditor in Slack to ask about your code, have it plan a change, or make the change and open a pull request. It also works on the rest of your team's Inference Bureau: it answers from the docs, sets up and runs automations, and creates apps and works with their records and actions, as you, asking before it changes anything.
Connecting Slack
On the Auditor page, open Automations and choose Connect Slack on the Slack card. Slack asks you to allow Auditor in your workspace; it connects as the workspace's app, not as you. Only owners and admins of your Inference Bureau team can connect it, and a Slack workspace works for one team.
You can also start from Slack: Add to Slack (or installing Auditor from Slack itself) asks you to sign in afterwards and pick the team it works for. Once it's connected, Auditor sends whoever installed it a message saying how to use it.
Auditor can post in any public channel. To use it in a private channel, invite it there first with /invite @Auditor.
Asking @Auditor
Mention @Auditor in a channel, message it directly, or type /auditor and your question. It answers in a thread: a line says what it's doing as it works (reading a file, searching the code, listing deployments), then the answer streams in. It can:
- Answer a question from the code and its history: how something works, what a pull request changes, what merged this week, what the latest deployment was.
- Write a plan for a change, with the files it touches and what it would need decided.
- Make the change and open a pull request. Once the pull request is deployed for preview (Vercel, or any host that reports builds through GitHub Deployments), Auditor posts the preview link in the thread, and again after each push.
A thread is one conversation. Reply in it to continue, with the earlier work in place; a reply sent while Auditor is 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. The conversations are runs of the team's Issue assistant automation, the same one that answers @auditor on GitHub issues and in Linear, so its model, instructions and limits are shared, and each run is on its page under Automations.
Your apps and automations
Auditor knows Inference Bureau, not only your repository. Ask it what something in Inference Bureau is or how it works and it reads the docs. Beyond that it works on your team, with the access of whoever asked:
- Automations: list them and their recent runs, set one up from a description (“every Monday at 9, post what shipped here”), change, pause or resume one, or run one now.
- Issues: read an issue and its comments, and comment on it, whether it's on GitHub (
#292,ib/web#292or its link) or in your Linear, Jira or Shortcut (ENG-12or its link), so “plan #292” or “post the plan on ENG-12” works without pasting it. Tickets need the tracker connected under Tickets in Auditor's settings. - Apps: list your apps and the recipes, create an app from a recipe or the starter, add a development environment, and in any environment find, count, create and update records, run actions, and read recent events and deploys.
A conversation continues in its thread like any other: ask it to list the reviews waiting for moderation, then to approve the first three.
Which repository
Auditor works in the repository the message names (ib/web, or web when only one repository has that name, or a link to a pull request), else the channel's repository, else your team's only repository. Set a channel's repository with repo owner/name in it. A pull request number in the message (#42) is read with it.
When none of those settles it, Auditor answers without a repository: questions about your apps, automations and the docs need none, so a team that uses Inference Bureau only for Apps can connect Slack too. Name a repository in a new message to have it read code.
Changes and auto mode
Anything that changes something of your team's (creating or running an automation, creating an app, writing records, running an action) waits for you. Auditor says what it will do, with Go ahead and Cancel under its answer; replying go ahead works too, and anything else is read as what to do instead. The change is made as whoever pressed Go ahead, with their access.
Auto mode, under Automations → Changes from chat, lets the kinds of change you tick run without asking: automations, apps and environments, records, actions, comments on issues, and deletes (off by default). Owners and admins can also press Always allow under a change to tick its kind. Changes to an app's production environment always ask.
Commands
list: your team's automations, when they run and whether they're on.run <name>: run an automation now. Its answer comes back in the thread. Anything after a colon goes to the agent:run Weekly summary: only billing.pause <name>andresume <name>.repo owner/name: the channel's repository.repoalone lists them.help.
A name can be the start of one, as long as only one automation starts that way.
Automations in Slack
Ask for something recurring or triggered by an event, such as “every Monday at 9, post what shipped here” or “when a pull request merges, post a summary”, and Auditor sets up the automation: its trigger, the repositories, what it does, and this channel to post to. It says what it will create and waits for Go ahead, as for any change; only owners, admins and members who manage Auditor can create one. Edit it afterwards under Automations like any other.
An automation whose outputs include Slack can post to a channel of the connected workspace. The agent writes the message, and Auditor posts it once per firing, or nothing when the agent has nothing to say. Reply in the message's thread to ask about it, and the run continues there. The recipes Weekly summary of what shipped, Post each merged pull request and Daily digest are set up for this; see Automations › Outputs.
Who can do what
Auditor matches the person in Slack to a member of your team by their Slack email address, or by the Slack account they linked to their Inference Bureau account. When it can't match someone, it sends them a message only they see with a link: they sign in, confirm, and from then on that Slack account is them on your team.
- Anyone in the workspace can ask and get answers and plans.
- Members of your team can also have it change code and open pull requests and issues, run automations, and work with the apps their access gives them (never an app's production unless they're an admin).
- 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, and gets 10 answers an hour: their questions are billed to your team like anyone's.
What it costs
Every model call is billed as inference to your team's Auditor key, like reviews; see Costs and spend caps. A conversation is limited by the Issue assistant's budget per reply and per month, and an automation by its own. The team's Auditor spend cap applies on top. Reading your apps and automations adds nothing beyond the model calls.
What it reads and keeps
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, the name and email of whoever wrote to it, and the names of channels when you pick one for an automation. It doesn't read other messages or channels. When a question needs them, it reads your team's automations and apps (their records included) with the access of whoever asked, and what it read goes to the model as part of the conversation. The bot token is stored encrypted. What a conversation started with is kept on its run in Auditor's activity log. The messages go to the model the run is routed to and aren't used to train models. The Privacy policy has the details.
Disconnecting
Disconnect on the Slack card deletes the stored token and the channels' repositories; @Auditor stops answering, and automations that posted to a channel post nothing until you pick a webhook or connect again. To remove the app from the workspace as well, remove Auditor in Slack under Tools › Apps. To have the conversations it kept deleted, email us from the Privacy policy.