Launch Week 1 — five features, five days
Jun 17, 2026 · Kenji Sakuramoto
Correction, 2026-09-21. The five features below shipped. The public
posts this article promised (Show HN, Product Hunt, Reddit, a Friday retro)
never went out, and the GitHub OAuth provider stayed switched off in
production until September. The post is kept as written; the current launch
plan and its gate are on the launch page, and the numbers
are in 9 signups in 5 months.
Correction, 2026-10-29: the Friday item named mushimushi.dev, a domain this
project never owned. mushi login opens the console at
kensaur.us/mushi-mushi/admin and you approve a code there; no key paste.
Mushi Mushi has been shipping quietly for a year. This week we stop doing that.
Five real features, five days, all announced publicly. The model is Supabase’s Launch Week — not a PR stunt, just a concentrated shipping cadence with enough momentum for the GitHub Trending algorithm to notice.
The five
Monday — open-source relicense. The server goes from BSL “source-available” to true OSI open source under AGPLv3. Read the post →
Tuesday — One-click MCP install. mushi setup writes .cursor/mcp.json (or .claude/, .continue/, or Zed’s settings.json) in one command. No UUID paste.
mushi setup # wires Cursor by default
mushi setup --ide claude # wires Claude Code
mushi setup --ide zed # wires ZedWednesday — Zero-config SDK init. <MushiProvider> needs no props if NEXT_PUBLIC_MUSHI_* (or VITE_MUSHI_*, EXPO_PUBLIC_MUSHI_*, etc.) are in your .env. The snippet in the wizard now reads exactly what was written to the file.
// Before: <MushiProvider config={{ projectId: '...', apiKey: '...' }}>
// After: <MushiProvider> ← reads from env automaticallyThursday — GitHub OAuth + onboarding. Signup with one GitHub click. New users land on /onboarding instead of an empty dashboard. Self-hosters get MUSHI_INIT_* env vars for headless bootstrapping.
Friday — mushi login. The CLI now opens the console in your browser, waits for you to approve the sign-in there, and verifies it. No more copying Project UUIDs from the dashboard.
mushi login # opens browser → approve → verifiedWhy now
The install path had two activation-blocking bugs:
- The “Add to Cursor” button on
/connectwas 404ing against a non-existent endpoint. - The CLI wizard’s printed snippet used hardcoded literal keys instead of
process.env.*— paste it and it broke.
Both are fixed. Launch Week is the announcement.
Numbers on Friday
Friday’s retro post will include: GitHub stars gained during the week, new signups, reports captured, and one honest “this didn’t go as planned” item. No rounding. No “we’re thrilled with the response.”
Follow along on Bluesky →