Bugsnag StrawberryHand the Bugsnag error severities to a companion
A companion works the 2 operations your Bugsnag account exposes. It can update an error severity and create a project, and every one of those waits on an approval card showing the error severity before it changes.
Open the error severity. Check it against something else. Write the change. Move to the next one. That is the Bugsnag afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a error severity until you approve it.
What it can do is exactly what Bugsnag exposes to an account you authorise and nothing beyond it: 2 operations, no reads and 2 writes. In practice that means it can update an error severity and create a project, and work across the error severities and projects.
The Bugsnag API stops at Bugsnag. 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.
Which Bugsnag error severities does a companion see?
In the tab.
Bugsnag exposes no read operation to a connected account, so a companion opens Bugsnag in the session you are already signed into and reads the screens you would.
The error severities are what most of this inventory is about, alongside the projects. A companion can hold all 2 of these operations and forty open tabs in the same pass, which is how an afternoon of Bugsnag admin becomes a queue you review.
Can it change a error severity without asking?
All 2 write operations wait for you.
A companion can update an error severity and create a project, and each one is staged on an approval card first: you see the error severity, the field and the new value before it lands in Bugsnag.
Nothing in Bugsnag is sent, changed or deleted on your behalf without that click, and a rejected card leaves the error severity exactly as it was. The gate is the same one on every surface, described at security.
- Update Error Severity
- Create Project
Can the error severities pass run every Monday?
Yes.
Saved as a routine, the Bugsnag error severities 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 operations playbook catalogues the other recurring shapes of the ticket queue, the Bugsnag error severities 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