MeshCore development team splits over trademark dispute and AI-generated code

· ai devtools · Source ↗

TLDR

  • MeshCore’s core team publicly split after contributor Andy Kirby secretly filed a trademark on the name and rebuilt the ecosystem using Claude Code without disclosure.

Key Takeaways

  • Andy Kirby filed a trademark application for “MeshCore” on March 29 without informing any team members, triggering the public rupture.
  • His rebuilt components – Companion, Repeater, Room Server firmware, web flasher, web config tools – are described as majority AI-generated via Claude Code, kept secret from the team.
  • The authoritative repo is on GitHub; Andy has never contributed to it, yet is claiming “official” status through his MeshOS line and controlled meshcore.co.uk domain.
  • After the split, Andy copied the team’s new meshcore.io site design using Claude despite being explicitly asked not to.
  • The project is large: 85+ firmware versions, 75+ hardware variants, 38,000+ nodes, 100,000+ active users since January 2025.

Hacker News Comment Review

  • Commenters largely separated the two issues: using Claude Code is not the core grievance; the secret trademark filing is, with AI use framed as a trust signal rather than a technical disqualifier.
  • The mesh networking trademark problem is seen as a pattern, not an anomaly – Meshtastic drew similar criticism for draconian trademark enforcement, and commenters expect more of these splits as projects grow.
  • Skepticism runs in both directions: some doubt the framing (AI code as betrayal), while others note Andy’s YouTube channel was already perceived as sensationalized and brand-building rather than community-focused.

Notable Comments

  • @nonethewiser: flags that conflating “vibe coded” with bad faith may be a rhetorical move – the trademark grab is the actual offense.
  • @the_gipsy: closed-source client app was a red flag from the start and a structural condition that made this outcome predictable.
  • @lukeasch21: recommends Reticulum as a protocol-layer alternative with a more principled distributed-networking design for those now reconsidering MeshCore.

Original | Discuss on HN