Skip to Content
v1.33.6 · shipped One-screen report · Looks like your app Read the changelog →
Admin consoleConnect
Walkthrough · 0:33Connect your AI editorPick your editor, add Mushi Mushi in one click or one command, then ask it to fix the latest bug.

Connect

Route: /connect (sidebar: Connect)

Scenario: Your repo is on GitHub, the SDK is installed, but your editor still can’t ask Mushi Mushi what broke, and you’re a couple of versions behind on @mushi-mushi/web. This page wires GitHub, the SDK, MCP, the CLI and upgrade PRs in one place.

A row of status pills at the top (App checked in, SDK version, Editor) says what is already connected. Below them, the page opens with a client picker: pick your AI client, then a lane (MCP / CLI / Skills). Connecting GitHub enables the Create Upgrade PR flow; the SDK and MCP sections work without it.

Client picker (3 lanes)

LaneWhat it does
MCPOne-click install for Cursor, VS Code, Claude Code, Windsurf and other clients (ClientConnectButton mints a scoped key, then opens a deeplink or gives you config JSON)
CLIThree commands to copy: npm install -g @mushi-mushi/cli@latest, mushi login, then mushi setup --ide <client>
SkillsCopy skill setup for the selected client

If your only key is an SDK key, a note under the picker offers Add an MCP key (mcp:read), which your editor needs to read this app’s reports.

Sections

#SectionWhat it does
1Client pickerMCP / CLI / Skills lanes (above)
2GitHubLink the repo so upgrade PRs, autofix and CI secret sync can use its token. Manage opens Integrations.
3SDK healthProblems that stop bug reports from arriving, each with a fix (see SDK health)
4Bug capture SDKFramework tabs and a copy-ready install snippet; Make a key and fill it in fills in the key
5Native app CI secretsDiagnose, and one-click sync of NEXT_PUBLIC_MUSHI_* into GitHub Actions
6Update centerPer-package freshness and Create Upgrade PR

Native app CI secrets

Capacitor, Expo, and React Native apps bake NEXT_PUBLIC_MUSHI_* at compile time. A missing secret silently disables initMushi() and the lime banner never appears in the store build.

The Native app CI secrets card calls GET /v1/admin/projects/:id/sdk-diagnostics and shows a fused verdict:

StatusMeaning
ci-secret-missingRequired var absent from GitHub Actions secrets/variables
native-never-seenWeb heartbeats exist but no capacitor:// / native UA
banner-disabledThe SDK banner is turned off in the SDK config
healthyAll CI secrets present and the SDK has reported from the expected origins
unknownNot enough to tell yet

One-click sync: POST /v1/admin/projects/:id/sync-ci-secrets mints a scoped ingest key and writes each required var via sealed-box encryption.

The Mushi Mushi GitHub App can read Actions secrets but not write them. Auto-write works when a fine-grained token with Secrets: Read and write is stored in the project’s settings. Otherwise the card shows the gh secret set commands to run and the env: block to add to your CI workflow.

See also: Self-hosting · AGENTS.md native CI section

SDK upgrade PR

When a package is outdated or deprecated:

  1. Click Create Upgrade PR on the Update center row.
  2. Backend enqueues sdk_upgrade_jobs → sdk-upgrade-worker bumps @mushi-mushi/* in package.json files only (never workspace: / file:).
  3. Draft PR opens on GitHub, auto-readied, status streams via SSE.

The bump edits package.json only. Add the lockfile helper workflow to your repo and the PR opens after your own package manager has refreshed the lockfile, so npm ci / pnpm install --frozen-lockfile pass.

CLI equivalent: see SDK reference → CLI (mushi upgrade for local bumps).

Quick path (5 minutes)

Connect GitHub

Press Connect GitHub, sign in to GitHub and pick your repository. The list shows only repositories you can open, with the one named like your app first. If the Mushi Mushi GitHub App is not on your account yet, GitHub asks you to install it first.

Install SDK

Copy the framework snippet → paste into your app → deploy or run locally.

Wire MCP

In the client picker’s MCP lane, click Add to Cursor (or your client’s button), restart the IDE, then run mushi doctor.

Wire CLI (SDK + env + MCP)

mushi connect saves credentials, writes the SDK env vars to .env.local and wires Cursor MCP. The Set up page’s CLI strip and the project success panel give you this command with your project ID filled in:

MUSHI_API_KEY=mushi_xxx mushi connect \
  --project-id <uuid> \
  --endpoint https://dxptnwrhwsqckaftyymj.supabase.co/functions/v1/api \
  --write-env --wire-ide --wait

Run mushi login first if you need to paste an API key interactively. SDK-only: mushi init --project-id <uuid>.

Verify

Click Send test report on the app’s row in Manage apps, or submit a report from your app.

Last updated on
Set upSetup copilot