The incident work, done and queued for one look
One sentence in, and a companion has been through the LinearB incidents, put them where you can read them, and marked the ones it was not sure about.
Open the incident. Check it against something else. Write the change. Move to the next one. That is the LinearB afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a incident until you approve it.
What it can do is exactly what LinearB exposes to an account you authorise and nothing beyond it: 2 operations, 1 read and 1 write. In practice that means it can create an incident.
The LinearB API stops at LinearB. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
Does it read the incidents or ask you for them?
1 of the 2 operations is a read.
Your account, not a guess at it: a companion can search incidents, and the full list below is the whole list, with nothing inferred from LinearB's documentation.
The incidents are what most of this inventory is about, alongside the incidents. A companion can hold all 2 of these operations and forty open tabs in the same pass, which is how an afternoon of LinearB admin becomes a queue you review.
- Search Incidents
Which incidents wait for your approval?
The one write operation there is waits for you.
A companion can create an incident, and each one is staged on an approval card first: you see the incident, the field and the new value before it lands in LinearB.
Nothing in LinearB is sent, changed or deleted on your behalf without that click, and a rejected card leaves the incident exactly as it was. The gate is the same one on every surface, described at security.
- Create Incident
Can it create incident on a schedule?
Yes.
Saved as a routine, the LinearB incidents pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The product and engineering playbook catalogues the other recurring shapes of the infrastructure checks, the LinearB incidents sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents