Questions, answered straight
Is it actually free?
Yes. The core (agent-mesh, published on npm as meshfleet) is MIT licensed — spawning, messaging, routing, receipts, and councils are free forever. Pro adds signed ledgers and attestation reports on top; the boundary is “mechanisms free, assurance paid,” and mechanisms never move behind the paywall.
Does it phone home?
No. Meshfleet runs entirely on your machine. No accounts, no telemetry, no analytics in the product, no network calls other than the model providers you already use. (This marketing site uses Cloudflare's cookieless Web Analytics; the product itself sends nothing.)
Only for OpenCode?
OpenCode is where Meshfleet is native today — it's the runtime with the acute pain (serial agents, the 30-minute timeout). But the core is a standard MCP server, so the surface area for other MCP hosts is small. Broader host support tracks real demand: if you want it somewhere specific, say so on GitHub.
How is this different from LangGraph or CrewAI?
Those are Python frameworks you build an application around. Meshfleet is infrastructure for a coding session: TypeScript, local-first, native to your editor's agent runtime, and agents are real OS processes rather than nodes in a graph. Messaging is witnessed — receipts and quorum votes are built in, not bolted on.
What's the story behind it?
Meshfleet is a ground-up TypeScript port of the coordination bus that ran our own internal fleet — 10+ agents running continuously for 40 days, 18,404 messages. That was the builder's fleet, not a customer's. The receipts-and-councils design comes straight from what that fleet actually needed, not from a whiteboard.
How many agents can I run?
Agents are OS processes, so the practical limit is your machine and your model-provider rate limits — fleets of ten-plus are routine in testing. Start with three to five; you'll feel the parallelism immediately.
Is it safe to let agents message each other?
Safer than letting them share a context window. Messages are typed and logged, every delivery leaves a receipt, and consequential decisions can require a council vote instead of one agent's say-so. The full security posture is documented in the repo; report anything to security@meshfleet.app.