MeshCore · 2026-04-23 · notable
MeshCore Team Splits After Core Developer Secretly Used Claude to Generate the Firmware
MeshCore's core team (38K nodes, 100K+ app users) split from developer Andy Kirby after he secretly used Claude Code to generate most of the ecosystem's code and filed for the MeshCore trademark. 258 HN points.
An open-source IoT project split after a core developer secretly vibe-coded most of the firmware with Claude and filed for the trademark.
Key specs
| Active nodes | 38,000 |
|---|---|
| App users | 100,000+ |
| Hn points | 258 |
| Hn comments | 140 |
What is it?
MeshCore is an open-source LoRa mesh communication system with 38,000 active nodes and over 100,000 app users. On April 23, 2026, the core team (Scott Powell, Liam Cottle, and others) published a post announcing the project had fractured. Core developer Andy Kirby had used Claude Code to generate the majority of the ecosystem's code — firmware, mobile apps, and web tools — without disclosing this to collaborators. He also secretly applied for the 'MeshCore' trademark. The remaining core team relocated to meshcore.io as the project's official home.
How does it work?
The split is a governance fork rather than a code fork. The core team retains the original codebase and community infrastructure under meshcore.io. Kirby's trademark application and 'MeshOS' branding create a competing claim to the project name. Community polls conducted in the Discord showed significant user distrust of undisclosed AI-generated code in safety-critical firmware. The core team committed to ongoing 'human-written software' with proper disclosure.
Why does it matter?
This is one of the first major open-source governance disputes to center explicitly on undisclosed AI-generated code in a deployed safety-relevant system. As Claude Code, Cursor, and similar tools become invisible in developer workflows, the question of whether AI code disclosure is a community norm — or obligation — in collaborative open-source projects is becoming urgent. The trademark application adds a commercial dimension that accelerated the split. Any team using vibe-coding in a shared open-source context will recognize the tensions here.
Who is it for?
Open-source contributors, IoT firmware developers, anyone managing AI-assisted development in collaborative projects