What's next
The Meshfleet roadmap. Shipped versions, the next release, and the path to v1.0. Dates are aspirational; everything is best-effort.
shipped
v0.6.0
— Fleet templates- ✓ save_fleet_template / list / get / delete / spawn_from_template
- ✓ Named collections of agent specs in the JSON ledger
- ✓ Template validation (lowercase + dashes, 1-32 agents)
shipped
v0.7.0
— Real-time + heartbeat- ✓ subscribe_inbox MCP tool (SSE push)
- ✓ Standalone HTTP SSE server with per-agent cap + heartbeat
- ✓ notifySubscribers hooked into send_message
- ✓ Heartbeat watchdog (auto-fail agents that miss N liveness checks)
shipped
v0.8.0
— Hardening push- ✓ Automatic retry with exponential backoff (max 3 attempts)
- ✓ Partial result recovery on startup (interrupted status)
- ✓ Ledger schema versioning (schema_version: 1, auto-migrate v0)
- ✓ route_work top_n parameter for fan-out
shipped
v0.8.1
— Skill taxonomy- ✓ Hierarchical skill matching with ancestor/descendant decay
- ✓ JSON taxonomy: { frontend: { react: [nextjs, remix] } }
- ✓ Wire into route_work planned for v0.9
shipped
v0.8.2
— Routing feedback loop- ✓ record_routing_outcome(agent_id, capability_key, success)
- ✓ Wilson-style score adjustment on future route_work calls
- ✓ RouteMatch.weight field exposes the adjusted score
shipped
v0.8.3
— Synonym expansion- ✓ Curated synonym table for 30+ common dev terms
- ✓ route_work now expands 'ui' to match a frontend agent, etc.
- ✓ Zero network cost, no ML dep, override via setSynonymOverrides()
shipped
v0.8.4
— Performance benchmarks- ✓ benchmark/bench.ts + BENCHMARKS.md
- ✓ v1.0 perf gates met: spawn bookkeeping 5.5ms p50, 10k messages no drops
- ✓ Known bottleneck: sendMessage rewrites full ledger (batch writes in v0.9)
shipped
v0.8.5
— Template versioning- ✓ Re-saving a template creates a new version (auto-increment)
- ✓ getFleetTemplate(name, version?) returns latest or specific
- ✓ listFleetTemplateVersions + deleteFleetTemplate(name, version?)
shipped
v0.8.6
— Template sharing- ✓ exportFleetTemplate writes portable meshfleet-template-v1 JSON
- ✓ importFleetTemplate reads, validates schema, inserts (auto-suffix on conflict)
shipped
v0.8.7
— Fleet dashboard TUI- ✓ npx agent-mesh-dashboard shows live fleets, agents, events
- ✓ Refreshes every 1s; ANSI in-place updates; Ctrl+C to exit
next
v0.9.0
— Scale + wire-up- ◐ Batch writes for sendMessage (fix 3.8ms/msg → 10k msgs < 5s)
- ◐ Wire skill-taxonomy into route_work (module built, not yet used)
- ◐ Wire synonyms into role/skill parsing (currently only description)
- ◐ Per-version fixture tests for COMPATIBILITY.md (CI run against each schema_version)
planned
v1.0.0
— Stable- ○ API freeze — tool names + input/output shapes locked
- ○ Distributed ledger option (libSQL behind a feature flag)
- ○ Optional auth token for MCP
Have an idea?
If something's missing or you'd like something prioritized, open a GitHub issue with the enhancement label. We especially want to hear about:
- →Real use cases (we add them to the website's /use-cases page)
- →Integration requests (specific MCP servers, frameworks, model providers)
- →Pain points in the current workflow (we'll see if the mesh can fix them)