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).
MCP-first (recommended)
Web
Mobile
How do I install the SDK?
Option A — zero copy-paste (recommended):
npx mushi-mushiThe wizard opens your browser, you click Approve, picks or creates a project,
installs the SDK, and writes .env.local — all automatically.
Option B — manual:
See Project ID & API keys for env var names per framework.
Troubleshooting
Not seeing what you expected?
Native builds bake Mushi env vars at compile time. Open Admin → Connect → Native app CI secrets and sync the missing vars, or run scripts/check-mushi-env.mjs in your prebuild.
Check that your project ID and ingest key match the console. Run mushi ping and Send test report on Projects. Use the SDK ingest key — not your editor MCP key.
Restart Cursor after editing .cursor/mcp.json. Pass MUSHI_PROJECT_ID in env. Mint an MCP read key in the console if you have not already.
Add your Anthropic or OpenAI key under Settings → API Keys. Self-hosters: confirm migrations are applied and the classify worker is deployed.