Walkthrough · 0:59From a bug report to a merged fixA real bug from Mushi Mushi’s own console: the plain-English diagnosis, the fix prompt for your editor, and the pull request that fixed it.

Bugs

Route: /reports (sidebar: Bugs)

The Bugs page is your Mushi Mushi inbox: every report, filterable by status, severity, category, component and free text. A recommended-action card at the top tells you what needs attention first (for example, critical items waiting for a human look).

Diagnosis + Fix hero

The top of every report detail leads with the brand promise — plain-English diagnosis + a paste-ready fix — as a single block:

“Here’s why it broke”: a 1–3 sentence plain-English diagnosis (the Stage-2 summary) with severity, category, and a confidence chip (NN% sure), plus the likely component.
“Fix it with your coding agent”: Copy fix prompt copies one self-contained prompt: what broke, why, the suggested fix, how to reproduce, the page, browser and OS, the most relevant console and network lines, the likely files, what “done” means, and a last step to open a PR that references the report. It works pasted into any agent (Claude Code, Cursor, Codex, Windsurf) with no MCP setup. Use with Claude Code, Use with Cursor (IDE deeplink or cloud agent) and Use MCP (the tool-driven prompt for agents with Mushi Mushi MCP connected) sit underneath.

Fail-graceful, by design. Accuracy matters most for this audience: a confident-but-wrong diagnosis is worse than none. So when classifier confidence is below 0.7 (or the summary is missing), the header flips to “Not sure yet — here’s what I’d check first” and lists the most concrete signals (component, reproduction hint, raw summary) instead of asserting a single root cause. The detailed sections below are unchanged; the hero just lifts the answer to the top.

Compact diagnosis preview

Press Space on the focused row in the list to open a preview drawer without leaving the list. It shows the same confidence-aware label and, when a fix brief is ready, a Copy fix prompt button, so you get the answer before you open the report.

Selecting a report opens the full detail view:

Recommended action: single-sentence guidance derived from the report’s status, severity and elapsed time, with one button.
Description + screenshot + breadcrumbs captured by the SDK. The screenshot is click-to-zoom.
Classification panel: category, severity, confidence, the LLM summary, component, reproduction hint, and the model and latency of the triage call.
Console / network / performance: always rendered, with informative empty states when the SDK didn’t capture data (so silence is visible).
Comments + presence: the header shows Also viewing: with anyone else on the same report, and comments arrive live.
Actions: change status, dispatch a fix, close as “Not a code bug”, and sync the report to your tracker (Jira, Linear, GitHub Issues or PagerDuty, whichever are connected in Integrations). When the report has no stack trace, source file or failed request, “Not a code bug” is the main button and dispatch moves to “Dispatch anyway”.
Fix card + pipeline flow: when a fix is dispatched, the detail page shows the active attempt, CI badge, and merge controls.
Related links: other reports for this component, this reporter’s history, the knowledge graph, the dispatched PR and the auto-fix pipeline.

Merging a fix from report detail

When a fix attempt completes with an open PR, the report detail page shows:

CI feedback: check-run status with Refresh CI status and a link to GitHub Actions.
Merge PR: confirm popover (squash by default). Disabled when the report is already Fixed or the PR is merged.
Primary attempt selection: if a retry failed after a successful PR open, the UI surfaces the mergeable attempt, not the failed retry.

The merge goes through the review gate: while the PR’s latest Opus review says hold, the merge is refused unless a team member (not a viewer) overrides it from the console with a reason. API keys (CLI, MCP) cannot override.

After merge, the report status becomes Fixed, the reporter widget receives a resolution notification, and fix.applied webhooks fire.

Equivalent CLI:


mushi fixes refresh-ci <fixId>
mushi fixes merge <fixId>

See Fixes → Merging from the console for the full sequence diagram and prerequisites.