Auditor in Linear

Connecting Linear

On the Auditor page, open Add-ons, add a Linear tracker under Issue trackers with your workspace's address (linear.app/your-workspace), and choose Sign in. Linear asks an admin of the workspace to install the Auditor app; it connects as the workspace's app, not as you, and Auditor refreshes the sign-in on its own. Only owners and admins of your Inference Bureau team can connect a tracker. app.inferencebureau.com/auditor/linear, the link in Linear's integrations directory, takes you there: it asks which team if you admin more than one, and opens the Linear tracker.

Then give each repository the ticket keys that point at it, on its Tickets tab: key ENG links ENG-412 in a branch name, pull request title or commit message to the Linear issue. Reviews then read the issue's title and text, as Descriptions › Tickets describes.

Use a token instead stores a personal API key. That is enough for reviews to read issues, but the app can't be mentioned or assigned issues through a token, so the rest of this page needs Sign in.

The comment on the issue

With Check changes against their ticket on, the review compares the pull request with its issue and lists up to three things the issue asks for that the change doesn't do, or says the change may not be the issue's work at all. Turn on Say it on the Linear issue too on the Linear tracker's page and that finding is also posted on the issue, so whoever wrote it sees it without opening GitHub.

There is one comment per pull request, edited on later reviews rather than added to. A pull request whose check finds nothing gets no comment, and one that found something earlier has its comment changed to say nothing is missing any more. The comment links the pull request and notes that it was compared from the issue's text, not the code, since the missing part may be planned for another pull request. It never fails the check.

Asking @Auditor

Mention @Auditor in a comment on an issue, or assign the issue to it. Linear opens an agent session on the issue, and Auditor shows it's working within a few seconds. It can answer a question (is the pull request ready to merge, what did review flag, what does this change touch), write a plan, open a GitHub issue, or make the change and open a pull request ending Fixes ENG-412, which Linear links back to the issue. Answers come from the code at the pull request's head.

It works in the repository the issue is about: the one of a pull request linked to the issue (and changes go onto that pull request's branch), else the GitHub issue the Linear issue is synced from, else a repository whose ticket key is the issue's prefix, else your team's only repository. When it can't tell, it says so in the session and asks you to link a pull request or set a ticket key.

Each Linear issue is one conversation. A follow-up in the session continues it with the earlier work in place; one sent while it's still working is read before its next step. The conversations are listed on the Linear tracker's page, each with what it read, changed and opened.

The work is done by the team's Issue assistant automation, the same one that answers @auditor on GitHub issues, so its model and instructions are shared; Edit instructions on the Linear page opens it. A repository's Tickets tab can switch Auditor in Linear off for that repository, give it its own instructions, or set its own limit per reply. Turning Auditor in Linear off for the team makes the app reply that it's off.

Who can have it change code

Anyone in the Linear workspace can ask and get answers and plans. Who can have it change code, on the Linear page, decides who can also have it change code, open pull requests and open GitHub issues:

• Anyone in the workspace. Connecting Linear is the team's consent, and the spending limits below still apply.
• Allowed people: Linear users whose email belongs to a member of your Inference Bureau team, is at one of the email domains you list, or is one of the addresses you list.
• No one: everyone gets plans and answers only.

Someone who isn't allowed is told in the session that Auditor will plan and answer, and that a team admin can add them.

What it costs

Every model call is billed as inference to your team's Auditor key, like reviews; see Costs and spend caps. On the Linear page you can set the most one reply may spend and a monthly limit, and see this month's spend over its conversations. A reply that reaches its limit stops and says what it got done; replying again continues from there. Blank means no limit, though a reply still ends after a few minutes of work. The team's Auditor spend cap applies on top.

What it reads and keeps

The Auditor app asks Linear for permission to read and write issues and comments, and to be mentioned and assigned issues. It reads the issue a pull request names, or the issue it's asked about: its identifier, title, description, links, the request and who made it, and, with Allowed people, that person's email. It doesn't read other issues, projects or members of the workspace. The access token is stored encrypted. What a conversation started with is kept on its run in Auditor's activity log. The issue's text goes to the model the run is routed to and isn't used to train models. The Privacy policy has the details.

Disconnecting

On the Linear tracker's page, Disconnect deletes the stored token; ticket IDs become links again, and @Auditor stops answering in that workspace. To revoke the app on Linear's side as well, remove Auditor under Settings › Applications in your Linear workspace. To have the conversations it kept deleted, email us from the Privacy policy.