MeshCore's $0 Trademark Grab Splits Development Team Over Secret AI Code
Andy Kirby just tried to trademark an open-source project he never contributed code to. And somehow, that's not even the most controversial part of this story.
On April 23, 2026, the MeshCore development team dropped a nuclear blog post announcing their split from Kirby over two explosive issues: his secret trademark application for "MeshCore" filed March 29, and his extensive use of AI-generated code from Claude that he never disclosed to the team.
Here's the kicker: Kirby controls the meshcore.co.uk domain and original Discord server, but has zero commits to the actual MeshCore GitHub repository. Yet he's been branding his downstream project MeshOS as "official MeshCore" while the real developers handled all the firmware development, PR management, and bug fixes.
The Claude Connection Nobody Saw Coming
The AI angle blindsided everyone. A Discord poll revealed the community majority strongly opposed undisclosed AI-generated firmware running on their hardware. One Hacker News commenter noted Kirby "kept secret" that his contributions were "majority vibe coded" - developer slang for heavy AI assistance.
Think about that for a second. Mesh networking operators were flashing firmware to critical infrastructure without knowing significant portions came from Claude. That's not just bad practice - it's a governance nightmare.
<> "The core team asserts the canonical MeshCore is the meshcore-dev/MeshCore GitHub repository, to which Andy has never contributed."/>
This split the community right down the middle. The core team launched meshcore.io for docs, blog, and their flasher tool, plus grabbed the meshcore.gg Discord. Meanwhile, Kirby sits on the original domain and server, creating maximum confusion for users.
The Real Story: This Was Always About Control
Everyone's focusing on the trademark drama, but dig deeper and you'll find something more troubling. This is what happens when open source projects lack clear governance from day one.
Kirby never contributed to the main repository. Ever. Yet he positioned himself as the face of MeshCore through domain control and community management. When the actual developers ship consistent releases and handle the technical heavy lifting, but someone else controls the brand identity, you're setting up for exactly this kind of explosion.
The trademark filing was just the match that lit the fuse. Filing on March 29 without telling the team who actually built the software? That's not miscommunication - that's a hostile takeover attempt.
What This Means for Developers
The Hacker News thread exploded to 231 points and 125 comments because this touches every open source developer's worst nightmare. Key takeaways:
- Domain control is real power - technical contributions mean nothing if someone else owns the brand
- AI code disclosure isn't optional anymore - the community will revolt if you hide it
- Trademark applications can weaponize open source disputes - even failed ones create chaos
For now, existing MeshCore nodes keep working fine. The firmware hasn't changed. But developers face a choice: follow meshcore-dev/MeshCore on GitHub for continued development, or stick with Kirby's MeshOS variant.
The trademark application is still pending - not granted yet. But the damage to community trust is already done.
The Bigger Picture
This split reveals how unprepared open source projects are for two major 2026 realities: AI tooling and brand protection warfare. The MeshCore team learned the hard way that technical excellence doesn't protect you from governance failures.
Kirby's side remains notably silent throughout this controversy. Communication has "fully broken down" according to sources. That radio silence speaks volumes.
Mesh networking just lost its most unified development effort to a trademark grab and secret AI code. The real tragedy? This was entirely preventable with basic project governance.
