Support

Where to get help with Meshfleet. Different questions go to different places — picking the right one gets you a faster, more useful reply.

Start here

Before reaching out, check:

→/docs — the full reference: install, concepts, API
→/quickstart — 5-minute end-to-end walkthrough
→/faq — 13 common questions with answers
→/changelog — what's in each release (look for "fixed" or "changed" notes)
→The event log at ~/.config/opencode/agent-mesh.events.log — the last 50 lines usually show the error

If you're stuck

Q&A "How do I...?" / "Is there a way to...?"

Open a GitHub Discussion. Use-cases, integration questions, and "is this possible?" questions all belong here. Other users can chime in if they have answers.

BUG "This is broken — here's how to reproduce"

Open a GitHub issue. Include what you expected, what happened, your Node version, OS, and the last 50 lines of the event log. Not for usage questions — use Discussions for those.

IDEA "I wish Meshfleet could..."

Open a GitHub issue with the enhancement label. Describe the use case first ("I want to do X"), not just the solution ("add Y feature") — this helps the maintainer understand whether to build it and how.

SECURITY "I found a vulnerability"

Do not open a public issue. Email security@meshfleet.app or open a private GitHub security advisory. See /security for the full process.

If you want to contribute

See /contributing for the full guide (dev setup, PR process, coding conventions, architecture overview). Short version:

→Good first issues are labeled good first issue on the tracker — pick one and open a draft PR
→Docs improvements are as valuable as code — typos, missing examples, unclear explanations all welcome
→If you want to add a new MCP tool, read the "Adding a new MCP tool" section in /contributing first
→If you find a security issue, follow the security process above (private, not public)

Commercial support

Meshfleet is a one-person project with no company backing. There's no commercial support tier, no SLA, and no paid consulting. If you need those, you're probably better off using a vendor product.

What I can offer for free: the best-effort support described above. If your use case is mission-critical, treat the project as you'd treat any other small open-source dependency — read the code, run your own tests, have a fallback.

If you want to sponsor the project or discuss a custom feature, email john@meshfleet.app.

Project status

As of v0.8.7 (July 2026):

→Stable enough for daily use — 181 tests, CI green, 10 releases, 10/10 starter issues closed
→Not yet v1.0 — one bridge release (v0.9.0) planned, then API freeze
→MIT licensed — use it commercially, modify it, redistribute it
→One maintainer — response times are best-effort, not guaranteed