kensaurus/mushi-mushi

**Your AI wrote it. Mushi tells you why it broke.**
When a user hits a bug, Mushi explains the cause in plain English and hands your editor a fix to start from.
Built for the vibe coder who ships fast with Cursor, Claude Code, Lovable or Bolt, so a bug costs five minutes instead of an afternoon.
Quick start · How it works · Docs · Demo · Why not Sentry? · Self-host · Vision
↑ a diagnosis: the root cause in plain English and a paste-ready fix prompt. Click to open the read-only demo.
How it works
1. **Capture.** A user taps the widget. Mushi records a screenshot, the route, their note, and the last console and network events.
2. **Diagnose.** Mushi writes the root cause in plain English with a fix prompt. Twenty reports of the same broken button become one row.
3. **Fix.** Your editor reads the diagnosis over MCP. If you want, an agent opens a **draft** PR that you review like any other.
It catches the bugs that never throw an error: the pay button hidden under the keyboard, the Save button tapped twice because nothing happened, the dashboard that takes 12 seconds.
Quick start
Then ask your editor: *"what's broken in prod?"*
The SDK needs two env vars (VITE_MUSHI_PROJECT_ID / VITE_MUSHI_API_KEY, or NEXT_PUBLIC_MUSHI_*; see examples/sdk.env.example). No Sentry, no LLM key, no monitoring stack. The hosted free tier covers 50 diagnoses a month with no card, or you can self-host.
Let your AI editor do the setup
Paste this into Cursor or Claude Code:
> Install the Mushi skills from github.com/kensaurus/mushi-mushi (npx skills add kensaurus/mushi-mushi), then run the mushi-setup skill to wire the Mushi SDK and MCP server into this app and send a test report to verify the connection.
The skills also add /mushi-debug (why ingest or MCP fails), /mushi-health (pass/fail across CLI, API and keys) and /mushi-integration (fix dispatch and the two-way loop).
Add it by hand (React shown; Vue, Svelte, Angular, React Native, vanilla JS, native)
Native SDKs (iOS, Android, Flutter) are a preview and install from this repository: see packages/ios, packages/android and packages/flutter. A runnable demo lives in examples/react-demo.
What's inside
| Package | For | What it does |
| --- | --- | --- |
| mushi-mushi | Setup | One-command wizard (npx mushi-mushi) |
| @mushi-mushi/react, vue, svelte, angular, react-native, capacitor | Your app | The bug widget for your framework |
| @mushi-mushi/web | Your app | The same widget for any site, no framework needed |
| @mushi-mushi/node | Your server | Reports backend errors into the same queue |
| @mushi-mushi/mcp | Your editor | Gives Cursor and Claude Code the diagnosis and fix tools |
| @mushi-mushi/cli | Your terminal | Setup, reports, fixes and health checks |
| @mushi-mushi/ux | Your app's screens | Runs your coding agent over every screen and keeps only measured improvements |
| packages/server | Backend | Supabase edge functions + Postgres. Hosted for you, or self-host |
Full list and maturity: SDK reference. Architecture: how the pipeline fits together.
Why not just Sentry?
> **Sentry is built around what the code threw, with a User Feedback widget and
> replay alongside. Mushi starts from what the user reported, ingests Sentry's
> errors too, explains each one in plain English, and hands your agent a fix
> prompt to start from. One queue, with or without Sentry.**
| | Mushi | Sentry |
| --- | --- | --- |