Contact
Different kinds of inquiries go to different places. Picking the right one gets you a faster, more useful reply.
Pick the right channel
security@meshfleet.app or a private GitHub security advisory. See /security for the full process. Do not open a public issue.
Open a GitHub issue with what you expected, what happened, and how to reproduce. Include your Node version, OS, and the contents of ~/.config/opencode/agent-mesh.events.log (last 50 lines) if relevant.
Open a GitHub issue with the enhancement label. Describe the use case, not just the solution — "I want to do X" is more useful than "add Y feature".
press@meshfleet.app for podcast, video, or written coverage requests. See /press for the press kit (logos, boilerplate, brand colors).
legal@meshfleet.app for license questions, terms interpretation, trademark use, or anything that needs a paper trail. See /terms and /license.
Open a GitHub Discussion (or an issue with the question label). Use-cases, integration questions, "how do I...", "is there a way to..." — all welcome.
john@meshfleet.app for anything that doesn't fit the above — say hi, ask about contributing, propose a collaboration, or just share what you're building with Meshfleet.
Response times
This is a small project maintained by one person. Realistic expectations:
- →Security reports: 48 hours acknowledgement, fix within 7 days for critical
- →Bug reports: 1-2 weeks, depending on severity and whether I can reproduce
- →Feature requests: considered at the next roadmap review (monthly); no commitment to implement
- →Press inquiries: within a week
- →Everything else: best effort, no SLA
The maintainer
Meshfleet is built by John Whitman. He's been building developer tools and AI agent systems since 2024. He maintains Meshfleet in his spare time, with no company backing and no monetization (yet).
He's responsive, fair, and happy to help. He's also one person, so patience is appreciated. If you need a guaranteed response time or commercial support, that's not something this project offers yet.