Launch Week
Every feature in Mushi’s history was shipped quietly. Launch Week is the corrective.
One week, five themed days, real shipping cadence — modeled on how Supabase built their community: consistent public shipping that compounds over time.
Launch Week 1 — what’s shipping
| Day | Feature | Status |
|---|---|---|
| Mon | Open-source relicense — server goes true OSI open source (AGPLv3) | ✅ shipped |
| Tue | One-click MCP install — mushi setup wires Cursor/Claude/Continue/Zed in seconds | ✅ shipped |
| Wed | Zero-config SDK init — <MushiProvider> with no props, env vars just work | ✅ shipped |
| Thu | GitHub OAuth + onboarding — signup in one click, straight to the wizard | ✅ shipped |
| Fri | mushi login — browser-guided credential setup, no UUID paste | ✅ shipped |
Launch Week 1 ran June 2026. Follow GitHub Releases and Bluesky for Launch Week 2 dates.
How it works
Mushi ships a themed feature every day for five days, announced on:
- Show HN (Tuesday 9am PT)
- Product Hunt (Wednesday 9am PT)
- Bluesky + X + LinkedIn (daily threads)
- dev.to / Hashnode (Wednesday longform)
- r/webdev, r/opensource, r/reactjs (Tuesday and Wednesday)
- awesome-lists (Thursday PRs)
A transparency retro ships Friday with real numbers (stars, signups, reports captured in the week).
The five-signal counter-position
Launch Week content centers on the four signals Mushi captures that your existing tools don’t:
Code-thrown errors → Sentry / Crashlytics
System telemetry → Datadog / New Relic
Product analytics → Firebase / Amplitude
User-felt friction → Mushi Mushi ← (the missing signal)Every launch post leads with the signal gap and shows Mushi closing it.
Want to be notified?
Star the repo — GitHub’s watch feature will ping you when a release drops.
Or follow on Bluesky → — every day-of post goes there first.
Run your own launch week
The full runbook lives in docs/marketing/launch-week.md — a Tuesday/Wednesday concentrated launch script with all copy templates, ready to paste.