Skip to Content
v0.8.0 · shippedNative mobile SDKs, optional Sentry enrichment, and bring-your-own keys/storage. Read the changelog →
ConceptsOverview

Concepts

When a user feels something break, Mushi captures it, explains it in plain English, and can hand your editor a fix — without another dashboard to babysit.

The loop in plain terms:

  1. Capture — users report what felt broken (shake, tap, or widget) with screenshot and context.
  2. Plain read — severity, category, and cause in English your team already uses.
  3. Connect — similar reports collapse to one row; hot spots emerge from the graph.
  4. Fix — optional agent drafts a PR; you merge, edit, or ignore.
  5. Verify — automated replay checks the fix before you ship.
  6. Remember — past fixes become rules your editor sees on the next PR.

Every step is observable, auditable, and improves over time — details below when you need the wiring diagram.

Last updated on