Launch Week
Correction, 2026-09-21. This page used to say Launch Week 1 ran in June 2026 with posts on Show HN, Product Hunt and Reddit. The five features did ship. The posts did not: no Show HN, no Product Hunt listing and no Reddit thread for Mushi Mushi ever went out. We are keeping the shipped list below and replacing the rest of the page with what actually happens next.
What shipped in June 2026
| Day | Feature | Status |
|---|---|---|
| Mon | Open-source relicense — the server moved to AGPLv3 (the post) | shipped |
| Tue | One-click MCP install — mushi setup wires Cursor, Claude Code, Continue and Zed | shipped |
| Wed | Zero-config SDK init — <MushiProvider> reads its env vars, no props | shipped |
| Thu | GitHub OAuth + onboarding — built; the provider stayed switched off in production until September | shipped, mis-configured |
| Fri | mushi login — browser-guided credential setup, no UUID paste | shipped |
Nobody outside the project was told. That is the honest summary, and it is why the launch model changed.
How we launch now: one post per release
A five-day blast assumes an audience that is already watching. We do not have one yet. So each release gets one public post on one channel, and the next release does not launch until the previous one has been measured. The number we publish after each is not stars; it is activated external projects per week, meaning a project owned by someone who is not us received its first real bug report and its owner opened the diagnosis.
| Release | Ships | The post | What we publish afterwards |
|---|---|---|---|
| R1 “Proof” | The no-signup demo verified in a private window; npx mushi-mushi on a fresh app reaching a first diagnosis in under five minutes, filmed; docs search returning no dead links; privacy policy and terms live; a first-reply promise on issues | Show HN, one Tuesday, 12:00–17:00 UTC. The URL is the demo, never the repo. | A blog post with the real numbers from that week, whatever they are: referrers, signups, activated projects. |
| R2 “Found” | The five comparison and how-to pages; the Mushi setup skill audited for Cursor and Claude Code; the Cursor plugin submitted | Product Hunt, plus value threads in r/cursor and r/ClaudeAI over the following two weeks (a thread first, the link in the comments) and a pitch to two developer newsletters carrying the HN numbers | Journey post #2: what N visitors did on a no-signup demo. |
| R3 “Loop” | A “Bug reports by Mushi” mark on the widget with a one-click opt-out; the events that let us measure whether it refers anyone; GitHub Discussions as the community home | A normal HN submission of journey post #3 (not a Show HN) and a dev.to cross-post | Journey posts #3 and #4, and the loop’s referral rate. |
The gate before R1
R1 does not post until every line here is true. The list is public so that if you read the Show HN and find one of these false, you can say so.
- The demo at
/connectloads in a private window with no signup and produces a diagnosis. npx mushi-mushion a fresh Next.js app reaches a first report and diagnosis in under five minutes, screen-recorded.- The two hero GIF slots on the landing page show that recording.
- The docs search tool our MCP server exposes returns zero dead links.
- The VS Code extension is either published or marked “deferred” in the distribution notes, and is not mentioned on HN until it is published.
- The privacy policy and terms of service return 200.
CONTRIBUTING.mdpromises a first reply on issues within 24 hours on weekdays.- This page tells the truth (done, 2026-09-21).
- The site’s structured data lists only accounts that exist.
- The Bluesky queue has no items scheduled in the past.
- The activation query returns a number, even if that number is zero.
What we will not do
- Post the same text to two places.
- Buy upvotes, hunters or ads.
- Resubmit a Show HN that fell off the front page.
- Claim a launch happened when it did not.
Want to be notified?
Watch releases on GitHub , read Announcements in Discussions , or follow Bluesky . The numbers from each release land on the blog.
Run your own
The runbook, with the presence rule, the hard rules and the post-mortem
template, lives in
docs/marketing/launch-week.md.