Quickstart

Start here if you vibe-code: the incident loop gets you from broken prod to a paste-ready fix prompt in Cursor — usually under a few minutes.

Or run the wizard: npx mushi-mushi (detects your framework, signs in via browser, writes env vars, optional test report).

Start here (MCP)

Incident loop — broken prod → diagnosis → fix in the editor
MCP server — wire Cursor / VS Code / Claude

Pick your stack

Web: React · Vue · Svelte · Angular · Vanilla JS

Mobile: React Native · iOS · Android · Flutter · Capacitor

CLI ↔ console: CLI console loop

How do I install the SDK?

Option A — wizard (recommended):


npx mushi-mushi

The wizard opens your browser, you click Approve, picks or creates a project, installs the SDK, and writes .env.local.

One key for both surfaces. The wizard mints a single API key for the SDK (sending reports) and the CLI (mushi doctor, mushi billing, etc.). Same key also works for read-only MCP tools in your editor.

Option B — manual:

See Project ID & API keys for env var names per framework.

The SDK needs only framework-prefixed project id + API key (see examples/sdk.env.example). The repo’s root .env.example is for self-hosting the backend — you do not need Supabase or an LLM key to use the SDK.

Troubleshooting

Not seeing what you expected?