Home
Route: /dashboard (sidebar: Home, first tab Today)
Scenario: You open Mushi Mushi in the morning and want to know in 30 seconds whether your app is up, whether anything broke overnight, and what needs you today.
Home is one page per app. It answers five questions without opening any other page: is the app up, what needs me, what is shipping, which pages have bugs, and who can reach it. Every number links to the list it counts. A part that is not connected yet is grey and its button says how to connect it; a part whose read failed says “Could not read” instead of showing a 0.
All of it comes from one call, GET /v1/admin/projects/:id/home.
Home has more tabs beside Today: Overview (all apps,
?view=apps), User activity (sessions, ?view=users),
Users & funnels (?view=funnels) and Weekly insights
(intelligence reports, ?view=insights). The old paths
/overview, /activity, /analytics and /intelligence open these tabs. This page
describes Today.
App card
A screenshot of your live site, the app’s name and address, its platforms (Web, iOS, Android) and the version Mushi Mushi last saw deployed.
- The screenshot is taken with your own Firecrawl key (Settings → Web tools); Mushi Mushi never uses its own key for it. It is stored privately and shown through a link that expires after an hour.
- While the live-site watch is on, Home takes a new screenshot once a week when you open it. Refresh picture takes one now (once every 10 minutes per app; viewers do not see the button).
- Without a screenshot the card shows the app’s store icon, then its site icon, then its initials, and says what is missing (“Add a Firecrawl key…”).
Health lights
Four lights, each with a word beside its colour:
| Light | Green | Amber | Red | Not connected |
|---|---|---|---|---|
| Site up | No broken pages | Last check failed, not checked for 3 days, or pages answer slower than 3 s | Pages the watch confirmed broken | Turn on the live-site watch |
| Errors today | New reports today (UTC), none critical | At least 5 new and double yesterday | Any critical report | Install the SDK |
| SDK sending | Your app checked in today | Quiet for 1–7 days | Silent for over a week | Create a key and add the SDK |
| CI on main | The latest run on your default branch passed | The test machine stopped (not a code failure) | A check failed | Connect your repo |
Click a light to open where its number came from (broken pages, the report list, SDK health, CI).
Needs you
At most five things, most costly first, each one sentence and one button: a broken live site, critical bugs waiting for a fix, fixes Opus put on hold, CI failing on main, an app that stopped sending, stuck fixes in the pipeline (agent failed, approved but not queued, red release train), and an SDK update. Pipeline items use the same groups and counts the Pipeline page shows, so the click lands on the same number. When nothing needs you, it says so.
While a setup step is still open, the setup card above Home names the step and its fix.
Release
- Stations: fix ready → CI → in train → merged → deployed, with the number of fixes at each and how many are stuck. Same stages as Pipeline.
- Train and deploy: the release train on the tracks (or the last one) and the version last seen live (Releases).
- Bugs waiting: one bar split by severity (critical, high, medium, low, not rated yet). Each colour opens the open bugs of that severity.
Pages
A small map of your busiest pages: visits in the last 7 days (from the SDK’s session
tracker), bug reports in the last 14 days, and pages the live-site watch found broken.
Page ids (/lessons/42) are grouped as /lessons/:id. With no visits, reports or
site checks yet, it says what fills it.
Access and details
Your repo and default branch, the people on the app, the SDK version you run against the latest one, your keys (label and last use only, never the key itself), and links to Fix history, User activity and, on plans that include it, the Audit log.
This week vs last week
Bug reports, critical bugs, fixes merged and (with session tracking) user visits, this week against last week. The change is green when it moved the right way for that row (fewer bugs, more fixes).
Recent activity
What happened, grouped into plain sentences: “3 fixes merged today”, “12 bug reports came in this week”, “2 deploys seen this week, latest v1.4.0”.
How this works
What Mushi Mushi does with a bug in four steps. Open by default only on a new app with no reports yet.
Common tasks
Morning check (1 minute)
- All four lights green? Move on.
- Clear Needs you from the top.
- Glance at Bugs waiting: any red (critical)?
After a deploy
- Check the version on the app card and under Release matches what you shipped.
- Watch Errors today and CI on main for the next hour.
A confetti burst and toast appear the first time a fix-worker PR is merged for your project: the “first merged fix” milestone.
Related pages
- To-do: all open actions in one list
- Bugs: the full bug queue
- Pipeline: every fix from report to deploy
- Mushi Mushi health: Mushi Mushi’s own AI and background job health