Incident loop

The incident loop takes you from "a user hit a bug in my live app" to "my AI assistant is fixing it". The bug arrives in your Mushi Mushi list with a plain-English read, and you paste a ready-made fix prompt into Cursor. It is the default path for vibe coders.

No MCP? Copy the fix prompt

Open the report in the console and click Copy fix prompt (under Fix it with your coding agent). Paste it into Claude Code, Cursor, Codex or Windsurf.

What the fix prompt contains

One self-contained prompt: the diagnosis, the suggested fix, repro steps, page and browser, the key console lines, likely files, and what “done” means. No MCP or editor setup is needed. The steps below are the MCP route, which lets the agent fetch the details and close the report itself.

Before you start

A Mushi Mushi project and API key (credentials).
At least one report: from the SDK, the test report npx mushi-mushi offers, or a Sentry alert.
MCP connected to your editor (MCP quickstart). The agent needs write access to mark the report fixed. Signing in through the hosted MCP (the default for Cursor and Claude Code) gives it; a key with only mcp:read does not.

The loop

Capture or pick a report

New project:


npx mushi-mushi

The wizard writes .env.local and offers a test report. At the end it offers to run mushi connect: say yes to wire Cursor’s MCP config and wait for the first heartbeat from your app.

Existing report: open Bugs in the console and copy its ID, or ask the agent “list recent mushi reports”.

You’ll see: a report ID, and the report in the console with a plain-English title.

Pull the fix context

In Cursor, ask:

Use Mushi Mushi MCP: call get_fix_context for report <uuid> and summarize the root cause in plain English.

get_fix_context returns the classification, repro steps, blast radius and a fixPrompt: a paste-ready fix brief built on the server. For most bugs you can paste fixPrompt straight into Cursor and skip to the last step.

You’ll see: the root cause in plain English, and a fixPrompt you can paste.

Get a deeper fix plan (optional)

Run the MCP prompt summarize_report_for_fix with the same report ID, or ask:

Run the Mushi Mushi prompt summarize_report_for_fix for report <uuid>. Give me a paste-ready Cursor prompt to fix it.

It combines get_fix_context, get_blast_radius and get_similar_bugs into one plan.

Paste and ship

Paste the agent’s output into a Cursor chat (or keep going in the same thread) and ask it to implement the fix. When GitHub is connected and Automatic fixes is on (console → Integrations), dispatch_fix can open a draft PR instead.

You’ll see: the code change in your editor, ready to review and commit.

Troubleshooting

Not seeing what you expected?