Use case · Engineering

Turn a pile of new issues into a sorted, labelled queue

To triage issues with AI agents, give a Brainwrite bot access to your issue tracker and repository. On a schedule, it reads new issues, groups likely duplicates, checks each report for reproduction steps and versions, and proposes a label, priority, and owner. You approve the changes it wants to make in GitHub, Linear, or Jira.

Download for Mac See the ready-made team

Issue triage

Every four hours, read new GitHub issues in our app repository. Mark likely duplicates, draft a request for steps to reproduce when they are missing, and suggest a label and owner. Ask me before changing anything.

Your Chief of Staff put a team on it

Nova· Chief of Staff
Dash· Triage bot
Atlas· Rigel, QA and Release Engineer

9 new issues since the last run
Likely duplicates: #1204 and #1211 match #1188 (same stack trace, same version)
Missing details: 3 reports lack a version; reply drafted, waiting for your approval
Proposed: #1207 bug, priority high, owner Mei (payments area)

DoneSaved as a routine: Every 4 hours. It starts paused until you turn it on.

An illustrated example. Your team works on your own files and apps.

Split scene: at 11:04 pm Bhavik Fuletra rubs his eyes alone at his desk; at 7:04 am he smiles with an orange coffee mug as illustrated AI agents Atlas and Dash sit beside him.

The job

Doing it yourself, and handing it off.

Doing it yourself

New issues arrive in every shape: a clear bug with steps, a one-line complaint, a feature request filed as a bug, the same crash reported four times. Someone has to read each one, search for duplicates, ask the reporter for a version, guess at a severity, and route it. It is careful work that nobody wants, so the queue grows until sprint planning forces a cleanup.

What the team does

Read issues opened since the last run
Group likely duplicates and explain the match
Draft a polite request for missing steps or versions
Propose a label, priority, and owner with a one-line reason

What waits for you

Labels, assignments, and comments posted to the tracker
Final priority for anything marked urgent
Closing duplicates

See it in the app

What it looks like in Brainwrite.

A real screenshot from a demo workspace.

Scout's built-in browser panel open beside the chat with a live tab on teams.brainwrite.in and the Let Scout use a browser switch on.

The team

Who's on it.

Your Chief of Staff picks the specialists the job needs. Each has its own role, instructions, model, and app access.

NovaIllustrated example
Chief of Staff
Takes the request, agrees the triage rules with you, and summarises each run.
DashIllustrated example
Triage bot
Reads new issues, searches for duplicates, checks for missing details, and proposes labels, priority, and an owner with a reason.
AtlasIllustrated example
Rigel, QA and Release Engineer
From the Ship Software Safely team. Reproduces the highest-priority reports on an isolated computer and separates root causes from symptoms.

How it runs

A run, step by step.

01
Connect the tracker
Connect GitHub, Linear, or Jira and grant the triage bot only the tools it needs, such as reading issues and adding labels.
02
Write the rules
Tell the bot your labels, severity scale, and who owns which area. It keeps them in memory you can edit.
03
Run on a schedule
A routine runs at the interval you set and posts each triage report to one results thread.
04
Approve the changes
Label, assign, and comment actions appear as approval cards in Ask mode. Approve, edit, or deny each one.

Start faster

Ready-made teams for this job.

Add a team from the library in one click. You see a preview first; routines arrive paused and connected apps stay off until you approve them.

Team libraryShip Software SafelyView the team →

What you'll connect

Apps this job uses.

FAQ

Questions about Issue triage

Can the bot close or label issues on its own?

Only if you let it. In Ask mode, actions in GitHub, Linear, or Jira become approval cards that show the action and its scope. You can also limit the bot to an exact list of tools per app, for example reading issues and adding labels but not closing them.

Is there a ready-made triage team?

Not a dedicated one. The Ship Software Safely team includes Rigel, a QA and Release Engineer who reproduces defects and separates root causes from symptoms, but its built-in routine is a pull request sweep. For triage, add a triage bot or ask your Chief of Staff to create one, and set its routine yourself.

Which AI model should run triage?

Any you have. Brainwrite starts the agent CLIs you already use, such as Claude, Codex, or Cursor, and you pick a model per bot and per thread. Triage reads a lot of text, so a faster, cheaper model can be a good fit. The usage chip shows token use and cost for each thread.

Built on