Status
Current state of the Meshfleet project: what's shipping, what's next, and what counts as "stable".
Current state
Latest release: v0.9.0 (July 2026). The npm package is published, the website is live, all CI checks are green (192 tests), and the dashboard TUI is verified against a live ledger.
Last incident: none. Meshfleet is local-first software, so there is no server to go down — your fleet state lives in your ~/.config/opencode/ directory.
What "stable" means for Meshfleet
Meshfleet is on a v0.9.x release. The version number means "API may change before v1.0" — but in practice, the core API has been stable since v0.8.0, and v0.9.0 only added tools (receipts, broadcast) without breaking existing ones. The remaining v0.9.x work is a bridge to v1.0: batch writes (the only known perf bottleneck) and the routing wire-up, then the API freezes. v1.0 follows shortly after.
For the official v1.0 stability criteria, see the /next page.
Recent activity
receipt, get_receipts, to_agent_id: "*"npx agent-mesh-dashboardFull history: /changelog · /releases · GitHub
Next: the v0.9.x bridge to v1.0
v0.9.0 shipped witnessed messaging (receipts + broadcast). Four bridge items remain before v1.0:
- ▸Batch writes for
sendMessage— the 3.8ms/msg bottleneck at 10k scale → 10k messages in < 5s (currently 35s) - ▸Wire
skill-taxonomyintoroute_work— the module is built; route_work doesn't use it yet - ▸Wire
synonymsinto role/skill parsing — currently only applied to the description keyword - ▸Per-version fixture tests for
COMPATIBILITY.md— load every v0.x ledger in CI
Once these land, the API freezes and the mesh is production-ready as v1.0. Background: the v0.9 preview blog post.
Get notified
Three ways to stay current:
- ▸RSS feed — blog + release posts
- ▸Watch the GitHub repo — release notifications + commits
- ▸/changelog — full change history per version