Mushi Mushi roadmap

Mushi Mushi is built in the open. VISION.md documents the full architectural target; code catches up release by release.

Currently shipping: @mushi-mushi/core and @mushi-mushi/web 1.33.x (Wave D complete; Wave E in progress). See the Changelog for what landed.

Live boards

Wave	Theme	Status
A	Vision air-gap, MCP correctness, RAG, sandbox	✅ Shipped
B	WASM SLM classifier, real-time collab, AG-UI, fine-tuning pipeline	✅ Shipped
C	Mobile SDKs (React Native and Capacitor on npm; iOS, Android and Flutter as unpublished previews), A2A protocol, SOC 2 readiness, data residency pinning (one live region today), BYOK, BYO storage	✅ Shipped, with the noted gaps
D	Plugin marketplace GA, docs site, Mushi Mushi Cloud GA, multi-repo coordinated fixes, PDCA console enhancements, QA coverage stories, SDK install & upgrade one-click, Skill-driven triage, Codebase Atlas	✅ Shipped
E	v1.0.0 cross-platform stable API, Launch Week, frictionless onboarding, self-hosting one-click	🔄 In-flight

Feature	Status	Notes
`@mushi-mushi/*` 1.0.0 stable API locks	🔄 In-flight	vue, svelte, angular, capacitor and node are 1.x on npm; `@mushi-mushi/react-native` is still 0.24
Frictionless onboarding	🔄 In-flight	GitHub/Google OAuth signup, auto-provisioned project+key; `mushi login` device flow shipped (Jul 2026)
Self-hosting one-click	🔄 In-flight	Railway / Render deploy button, `MUSHI_INIT_*` headless bootstrap
Launch	🔄 In-flight	One public post per release, not a coordinated week (how we launch). First posts went out 2026-10-29 on r/SideProject, X and LinkedIn; Show HN is not posted yet

Feature	Status	Notes
Agent PR review	✅ Shipped	Claude Opus reviews every cloud-agent pull request on your own key; a hold blocks merging from Mushi Mushi
Review follow-ups	✅ Shipped	A “fix first” pull request goes back to a new agent once, with the findings
Spend-down safety stop	✅ Shipped	Spend-down pauses an app whose agent pull requests review poorly; 7-day scoreboard per key
All-apps AI keys	✅ Shipped	One key you own serves every app in the organizations you own (BYOK)
CI runners	✅ Shipped	`/ci` shows where tests run and why a fix waits; a stopped test machine is never called a failed fix; `mushi runner add`
Verified merge	🔄 In progress	An agent pull request merges on its own only with proof: a test that fails without the fix and passes with it, no weakened tests, a small diff, and two AI reviews that can stop it. Off by default
Run Mushi Mushi on your own machines	⏭ Planned	A local-only mode with a self-test that proves nothing leaves your network (`mushi local verify`)

One-click SDK install & upgrade — npx mushi-mushi + npm create mushi-mushi wizard, SDK upgrade PRs from the Connect hub
Skill-driven triage — skill-sync, classify-report Stage 2, pipeline runs, kenji skills integration
Codebase Atlas (/explore) — semantic codebase search, ask, tour, and knowledge surface
sdk-versions-cron — daily npm sync keeps SDK freshness chips accurate
Backend drift scanner — daily schema snapshot diff, gate_findings of type schema_drift
MCP tool surface — @mushi-mushi/mcp, mcp:read + mcp:write scopes, tools grouped into feature groups you switch on (see @mushi-mushi/mcp for the current, catalog-sourced tool count)

Native SDKs — iOS (Swift), Android (Kotlin) and Flutter implementations in the repo, plus the Capacitor plugin on npm. The three native SDKs are previews: publishing to CocoaPods / SwiftPM release tags, Maven Central and pub.dev is still open
A2A discovery — a2a-push-notify edge function; agents can subscribe to Mushi Mushi events as A2A peers
SOC 2 readiness module — retention policies, data-subject request tracking and nightly snapshots of five controls (RLS coverage among them). Not a certification
Data residency — a region (US / EU / JP) is picked at project creation, but Mushi Mushi Cloud runs one production cluster in Tokyo today; EU and US clusters are reserved, not live (details)
BYO storage — S3, Cloudflare R2, GCS, MinIO, or Supabase Storage per project
BYOK — project-scoped Anthropic + OpenAI keys via Supabase Vault
PDCA runner — closed-loop iteration engine: fix → judge → promote, visible in the Iterate console page
Drift scanner — drift-walker + contract-graph-builder detect API contract drift against live routes
QA coverage stories — define and schedule user-story tests from the admin console

See VISION.md (positioning constitution) and Concepts → Architecture for the architectural target.