Bugsnag plugin

Copies each bug Mushi Mushi triages into Bugsnag as an error, and marks it fixed when the fix merges.

Not in the Mushi Mushi Cloud Marketplace yet. The console has no Bugsnag listing, so you can’t install it from there. On a Mushi Mushi server you run yourself, add a plugin_registry row for it and install it like any listed plugin. To bring Bugsnag errors into Mushi Mushi, use @mushi-mushi/adapters instead.

Setup (self-hosted Mushi Mushi)


npm i @mushi-mushi/plugin-bugsnag
export MUSHI_PLUGIN_SECRET=...      # the signing secret set when the plugin is installed
export BUGSNAG_API_KEY=...          # Bugsnag Data API token
export BUGSNAG_PROJECT_SLUG=...     # from your Bugsnag project URL
export ADMIN_BASE_URL=https://...   # optional: console URL for report links
npx -p @mushi-mushi/plugin-bugsnag mushi-plugin-bugsnag

Point the plugin’s webhook URL at https://<your-host>/mushi/webhook.

Package

@mushi-mushi/plugin-bugsnag

Events

Event	Action
`report.classified`	Create a Bugsnag error (grouping hash `mushi-<projectId>-<reportId>`) with a link back to the report, through `POST /v2/projects/<BUGSNAG_PROJECT_SLUG>/errors` on the Data Access API
`fix.applied`	Set the error’s status to `fixed`

The report → error mapping is kept in memory unless you pass your own cache to createBugsnagPlugin(cfg, cache), so after a restart fix.applied is skipped for older reports.

We have not confirmed the create call against a live Bugsnag account, and Bugsnag documents its SDKs as the usual way to record errors. Check your server log after the first report.classified before you rely on it.