Skip to Content
v1.33.6 · shipped One-screen report · Looks like your app Read the changelog →
Admin consoleSettings
Walkthrough · 0:29Set it up once in SettingsWhere bug alerts go, how bugs are sorted, and how much Mushi Mushi may spend.

Settings

Route: /settings (sidebar: Settings)

Scenario: Your widget copy feels off, you want your own AI keys on the bill, and Slack should ping the channel when a critical bug lands. This page holds every Mushi Mushi project setting: alerts, keys, widget and developer toggles.

The page has six tabs: General, AI keys, Web tools, Voice reports, SDK & connection and Display & sidebar. The tab you pick is saved in the URL (?tab=). Old links still work: ?tab=firecrawl and ?tab=browserbase open Web tools, ?tab=health and ?tab=dev open SDK & connection, ?tab=keys opens AI keys and ?tab=labs opens Display & sidebar.

Tabs

General

Bug alerts (Slack channel), error tracking (Sentry), an optional read-only link to your Supabase database, and Bug sorting: the AI models for triage, the quick check, the judge and fixes, the quick-check confidence, grouping of similar bugs and fix branch names. It also holds daily limits for Firecrawl and test writing, the feedback widget’s “Bug reports by Mushi Mushi” line, and, behind Fixes and CI → Show, the pull request review, verified merge, CI cost and CI policy settings.

Spend limits (project admins) cap what the project spends. Leave a field empty for no limit.

LimitWhat happens when it is reached
Monthly AI budgetEvery AI call for the project (triage, fixes, chat) stops until the 1st of next month (UTC). New reports get a short explanation instead of a diagnosis. Calls on your own API keys count too.
Auto-fix spend limit, last 30 daysMushi Mushi stops starting fixes on its own. Fixes you start yourself still run, and show the 30-day spend.
Automatic fixes per daySame, counted per UTC day. A limit of 3 allows 3 automatic fixes.
Ask me before fixes that may cost more thanA high or critical fix estimated above this waits for your approval, including fixes you start.

New projects start with $2 per 30 days and 3 automatic fixes a day.

If Mushi Mushi cannot read this month’s spend (a database error), the AI call goes ahead and the failure is reported to the operator’s error monitoring. A temporary read failure never stops triage, and it never passes unnoticed.

AI keys

Your own keys for Anthropic, OpenAI, OpenRouter, Cursor, Firecrawl, Browserbase and Supabase. Keys are stored encrypted in Supabase Vault, and after saving the list shows only a short hint of each key. A key can belong to one app or be shared with your other apps; an app’s own key is tried first. The Cursor row also holds spend-down mode (see Spend credits).

Web tools

  • Firecrawl (web pages): your Firecrawl key, the websites it may read, and the pages per lookup. Firecrawl reads public web pages while Mushi Mushi diagnoses a bug.
  • Known fixes on the web: the Search the web for known fixes switch.
  • Browserbase (cloud browser): runs scheduled tests in a cloud browser when a story’s provider is browserbase. Keys go through GET|PUT /v1/admin/byok/browserbase.

Voice reports

Report bugs by voice from your phone, Telegram or Slack. See Voice intake.

SDK & connection

Check the connection (whether this browser reaches Mushi Mushi and where your data lives), Install the bug widget (a link to Connect, where the install snippet lives, and the API address to copy), Send a test bug, and Debug logging (this browser), which logs to the browser console. Debug logging is stored in this browser only; it is never sent to the SDK or end users.

Display & sidebar

How the console looks in this browser: theme (system, dark, light), density, table rows and focus mode (Ctrl/Cmd + . toggles it, Esc exits). The same controls open from your name at the foot of the sidebar. Below them, choose which extra pages (Labs) stay in the sidebar. Every other page is under More pages in the sidebar. ?tab=labs links still open this tab.

Changing a key

  1. Open the AI keys tab.
  2. Add the new key on the provider’s row and save it.
  3. Open Mushi Mushi health → Probe now to verify the new key works.

Do not paste a Supabase service_role key here. That key bypasses all row-level security and must only be used server-side. The Supabase row asks for a scoped, read-only access token, as its instructions describe.

Last updated on
ResearchTeam