Skip to Content
v1.33.6 · shipped One-screen report · Looks like your app Read the changelog →
Admin consoleManage apps
Multi-project workspace with inline test-report CTAs · · open live demo ↗

Manage apps

Route: /projects (sidebar: Apps › Manage apps)

Scenario: You’re setting up Mushi Mushi for a new mobile app. You need to create the project, grab an API key, paste the install snippet into your codebase, and send a test report to confirm everything is wired up, all before your next PR review.

This page handles the full project lifecycle: create, configure, monitor, and (if needed) delete. It has three tabs: Overview, Your projects (one card per project) and New project.

Project card

Each project gets a card showing:

FieldDescription
NameRename edits it inline. Renaming does not change the slug or any URLs.
SDK version badgeok, outdated, deprecated, or unknown
PDCA bottleneckChip showing where reports are stuck in the loop (classify → fix → verify)
Repo stripConnected repo URL, default branch, index health (ok / stale / failed / off / never), indexed file count
30-day severity chipsCount of critical / major / minor / trivial reports
7-day report trendArrow indicating whether report volume is rising or falling
Sentry connectedBadge if a Sentry DSN is wired in
Plan tier + regionThe project’s current plan and data-residency region

Creating a project

Use the New project tab here, or Set up:

  1. Enter a name and click Create project.
  2. A success panel appears with your Project ID (UUID), the report:write key that was made for you, and a prefilled mushi init command.
  3. If no key was made, click Generate API key. SDK keys are made here or on Set up, not in Settings (Settings → AI keys is for your own provider keys).

When the CLI wizard opens your browser, it lands on ?setup=cli with the same success panel flow.

Local dev console: http://localhost:6464 after pnpm dev. Override with MUSHI_CONSOLE_URL in the CLI. See CLI ↔ console loop.

API keys

Each project card lists its API keys:

ColumnDescription
PrefixThe start of the key (the full key is only shown once, at creation)
ScopesWhat the key may do (see the presets below)
CreatedTimestamp
RevokeConfirmation, then an undo toast for 8 seconds before the key stops working

Generate a key:

  1. Pick a scope preset: SDK ingest, MCP read-only, MCP read + write, Voice intake, Runner health or Local worker.
  2. Click Generate API key.
  3. Copy the key immediately. It is only shown once in plaintext.

SDK ingest keys are for use in your frontend/mobile SDK. MCP read + write keys grant write access to Mushi Mushi via MCP tools: treat them like a service-role key and store them only in server-side environments.

SDK install configurator

Each project card includes a live SDK snippet configurator, with the in-widget assistant settings under it:

  • Framework tabs: a script tag, React, Vue, Svelte, React Native, Expo, Capacitor, Node, Express, Fastify, Hono and plain JavaScript
  • Position picker: where the feedback button appears on screen
  • Theme: light / dark / system
  • Copy snippet: copies the ready-to-paste install code

Send test report

Click Send test report on any project card to fire a synthetic report through the full ingest pipeline. It checks ingest only and does not mark the SDK as installed. The result appears as a new row on Bugs. Test reports are limited to 10 per user per hour.

Deleting a project

Delete the project, type its slug in the confirmation dialog, and confirm. An undo toast gives you 8 seconds to change your mind; only owners and admins can delete. After that, deletion is irreversible: all reports, fix attempts and QA stories for the project are removed.

Common tasks

Connecting a new app (5 minutes)

  1. On New project (or the first screen of Set up), enter a project name and create it.
  2. Copy the Project ID and the key from the success panel. If no key was made, use Generate API key (report:write) and copy it immediately.
  3. In your app repo run MUSHI_API_KEY=<key> mushi connect --project-id <uuid> --endpoint <api-url> --wait (or mushi init --project-id <uuid>). --project-id and --endpoint are required.
  4. Click Send test report to confirm reports arrive.

Sharing with a teammate who only needs read access via AI

  1. Select the MCP read-only preset → Generate API key.
  2. Share the key; they configure it in their AI assistant using the snippet on the Editor agents page.

Rotating a compromised key

  1. Revoke the exposed key and confirm. It stops working once the 8-second undo toast closes.
  2. Generate a new key with the same scope.
  3. Update the key in your app’s environment variables.
  4. Click Send test report to confirm the new key works.

Actions at a glance

ActionWhere
Create projectNew project tab → name → Create project
RenameRename → edit inline → Save / Cancel
Switch to (set active)Switch to button on the card
Jump to ReportsReports link chip
Jump to IntegrationsIntegrations link chip
Jump to SettingsSettings link chip

API

GET  /v1/admin/projects
POST /v1/admin/projects            { name }
PATCH /v1/admin/projects/:id       { name }
DELETE /v1/admin/projects/:id      { confirm_slug }
POST /v1/admin/projects/:id/keys   { scopes?, label? }  (scopes default to ['report:write'])
DELETE /v1/admin/projects/:id/keys/:keyId
POST /v1/admin/projects/:id/test-report
Last updated on
Team membersBilling