The MeshCore open-source mesh networking project fractured after a core contributor secretly used Claude Code for majority of new components and filed a trademark without team consent.
The MeshCore development team publicly announced a split with contributor Andy Kirby, who built major ecosystem components — standalone devices, mobile app, web flasher, and config tools — predominantly using Claude Code (AI-generated 'vibe coding') without disclosing this to the team. Kirby separately filed a trademark application for 'MeshCore' on March 29 without informing collaborators, and is now asserting brand ownership through his MeshOS product line. Communication between Kirby and the core team has fully broken down. The original team is relocating to a new website and Discord server, contesting the 'official' status of Kirby's trademark claim.
This is the first high-profile case of AI-generated code (via Claude Code) creating a trust rupture inside an active open-source project — not because the code was bad, but because its origin was hidden. The MeshCore community poll showed clear user skepticism toward AI-written firmware. For developers contributing to or depending on open-source projects, this signals that disclosure of AI tooling is becoming an expected norm, not a personal choice. Embedded in IoT/mesh networking contexts where firmware quality and auditability matter, the stakes of undisclosed AI code are higher than in typical web apps.
If you contribute to any open-source project and use AI tools like Claude Code or Copilot, add an explicit AI usage policy to your CONTRIBUTING.md this week — before your community raises it adversarially.
Suggested exercise · not independently tested. Access requirements and costs may vary.
Go to claude.ai and open a new conversation
Paste this prompt: 'Write a concise CONTRIBUTING.md section (under 200 words) for an open-source embedded firmware project that sets clear expectations about AI-generated code: when it's allowed, when it must be disclosed, and how it should be reviewed before merging.'
Review the output and adapt it to match your project's existing tone and governance structure
Tags