Skip to Content
v0.8.0 · shippedNative iOS / Android / Flutter / Capacitor SDKs, A2A discovery, SOC 2 readiness, residency, BYO storage, BYOK. Read the changelog →

Mushi · little bug helper

Your users feel a bug. You see a fix.

When something’s off — a slow screen, a button that doesn’t respond, a layout that breaks on one phone — your user wants to tell you. Mushi gives them a way that doesn’t involve email, support tickets, or screenshots in Slack.

Sentry sees what your code throws. Mushi sees what your users feel. The two are designed to compose: Mushi’s classifier reads Sentry breadcrumbs, and Sentry User Feedback events forward into Mushi via webhook — so nothing about your existing setup has to change.

Try it in 60 seconds

Drop the provider in. Your users get a shake-to-report widget the same day.

React

Same widget, same reports, in the framework you already ship.

Vue, Svelte, Angular

Shake detection, offline queue, and a Sentry bridge already wired up.

iOS, Android, Flutter

Triage from inside Claude, Cursor, or Codex without leaving your editor.

MCP server

Where Sentry stops, this picks up.

LayerSentry aloneMushi
What it seesErrors your code throwsFriction your users feel
What lands in your queueA stack traceA short user note plus the screenshot they were looking at
Repeat bugsEach one shows up as a new issueThe same broken button collapses to one row
Closing the loopAssign a ticket and remember to updateAn optional draft PR you can merge or ignore
From your IDECopy the issue ID into CursorCursor reads the report and proposes the diff
Where it runsTheir cloudYours, ours, or both

What happens after a user reports something

  1. Step 1CaptureA frustrated user shakes their phone instead of writing a support email. Mushi grabs what they saw and what they were doing.
  2. Step 2ClassifySeverity, category, and a root-cause hint arrive in plain English — the same labels your team already uses on the bug tracker.
  3. Step 3ConnectDuplicates collapse against past reports. The same broken button reported twenty times shows up as one row, not twenty.
  4. Step 4FixAn optional agent drafts a PR. You review it like any other PR — and merge, change, or close it.

See Concepts → Architecture for the wire-level sequence diagram and component-by-component spec.

React