The MeshCore Split
How a trademark filing, undisclosed AI-generated code, and a breakdown in communication fractured one of amateur radio's fastest-growing mesh networks.
MeshCore launched in January 2025 and grew at astonishing speed — 38,000+ nodes and 100,000+ active users in under 18 months. Behind the scenes, a dispute over a secret trademark application, undisclosed AI-generated code, and brand ownership brought the project to a public fork. This page explains what happened, who is involved, and what it means for the community.
A Timeline of Events
Key moments in the MeshCore project's fracture.
MeshCore Launches
Scott (firmware founder), Liam Cottle (app), Recrof (map/flasher), FDLamotte (Python tooling / STM32), and Oltaco (bootloader) begin building the project. Andy Kirby joins in a community/brand capacity, building and managing the meshcore.co.uk site as the public-facing hub.
Rapid Growth & Hidden AI Usage
The team ships 85+ firmware versions supporting 75+ hardware variants. The project grows to 38,000+ nodes globally and 100,000+ app users. Andy begins using Claude Code (an AI coding assistant) extensively to rewrite companion app components, the web flasher, web config tools, and standalone device firmware — but does not disclose this to the core team.
Secret Trademark Filing
Andy Kirby files a trademark application for "MeshCore" without notifying any other team member. (Source: UK trademark filings.)
Discovery & Breakdown
The core development team discovers the trademark application. Attempts at discussion break down. Communication with Andy ceases entirely.
Official Split Announced
The core team publishes a public statement at blog.meshcore.io, officially announcing the split. They launch meshcore.io as the new official home. Andy is identified as no longer part of the core team.
Website Design Copied
Andy Kirby copies the visual design of the newly launched meshcore.io website — using Claude — despite explicit requests from the core team not to do so.
Andy's Video Response
Andy publishes a video response. He frames the trademark filing as brand protection (not code ownership), acknowledges communication "could have been better," and contests the core team's characterization of his contributions. NodakMesh covers both sides.
Unresolved
The trademark application remains unresolved. Core team continues active development at meshcore.io. Andy's MeshOS products remain at meshcore.co.uk. The canonical GitHub repo is github.com/meshcore-dev/MeshCore.
The Core MeshCore Team
These are the engineers whose code constitutes the canonical MeshCore project on GitHub (meshcore.io).
Scott
(ripplebiz)
Firmware Engineer & Founder. Architected the core MeshCore C++ library and the Ripple firmware. Primary author of the GitHub repo.
Liam Cottle
App Developer. Built and maintains the official MeshCore app for Android, iOS, Windows, Mac, Linux, and Web.
Recrof
Map & Tooling. Developed the official MeshCore Map portal and the Web Flasher tool.
FDLamotte
Python Tooling & STM32. Responsible for Python-based developer tools and STM32 hardware support.
Oltaco
Bootloader. Works on the device bootloader layer that underpins hardware bring-up.
Andy Kirby: Role, Actions, and the Dispute
Andy Kirby was not a core firmware engineer — by his own admission — but played a significant community and brand-building role. The following summarizes documented actions cited in the core team's public statement, alongside Andy's stated response.
What the Core Team Alleges
- • Extensive, undisclosed use of Claude Code (AI) to rewrite ecosystem components including companion app, web flasher, web config tools, and standalone firmware — described as "majority vibe coded"
- • Secret trademark filing for "MeshCore" on 29 March 2026 — not disclosed to any other team member
- • Continued use of the word "official" in MeshOS marketing despite no code contributions to the canonical GitHub repo
- • Copied the look and feel of the newly launched meshcore.io site using Claude, after being asked not to
Andy Kirby's Stated Position
May 2026
- • Has never claimed to be a core firmware developer; credits Scott, Liam, and the team fully for the firmware
- • His role was brand, community growth, manufacturer relationships, onboarding, and video content
- • The trademark filing was intended to protect the brand and ecosystem — not to claim ownership of the open-source code
- • The filing came in the context of the .io site appearing "without coordination," which he saw as fragmentation
- • Acknowledges: "Could communication have been better? Probably."
- • No malicious intent stated; disputes the characterization of his contribution as purely commercial
Undisputed Facts
- • Andy Kirby has zero direct code commits to the canonical github.com/meshcore-dev/MeshCore repository
- • A trademark application for "MeshCore" was filed on 29 March 2026 — not disputed
- • Andy controls meshcore.co.uk and the original MeshCore Discord server
- • meshcore.io and the new Discord (meshcore.gg) were launched by the core team after communication broke down
- • A community Discord poll showed majority opposition to undisclosed AI-generated firmware
Two Ecosystems: What Each Side Offers
A side-by-side comparison of the two diverging projects.
| Topic |
meshcore.io
Open Source
Core Team
|
meshcore.co.uk / MeshOS
Proprietary / Contested
Andy Kirby
|
|---|---|---|
| Codebase | MIT-licensed, fully open source on GitHub | Closed / proprietary components; AI-generated |
| GitHub Repo | github.com/meshcore-dev/MeshCore (canonical) | No direct contributions to canonical repo |
| Firmware Authorship | Hand-crafted by human engineers | Extensively AI-generated (Claude Code) — not disclosed initially |
| App | Official MeshCore App by Liam Cottle (Android, iOS, Desktop, Web) | Separate MeshOS app |
| Web Flasher | flasher.meshcore.io — maintained by Recrof | Separate web tooling at meshcore.co.uk |
| Map | map.meshcore.io — maintained by Recrof | Separate map |
| Discord | meshcore.gg (core team) | Original server (Andy controls) |
| Documentation | docs.meshcore.io | meshcore.co.uk docs |
| Trademark Claim | None — relies on GitHub as source of truth | Trademark application filed 29 Mar 2026 (pending) |
| "Official" Status | Asserted by core team; GitHub repo is source of truth | Claimed by Andy via trademark and "official" MeshOS branding |
| Hardware Focus | 75+ variants across multiple manufacturers | Primarily T-Deck hardware (LilyGO) |
| Licensing | MIT — free to use, modify, distribute | Terms not fully public |
Guidance for Operators & Community Members
If you run MeshCore nodes, use the app, or contribute to the ecosystem, here's the practical picture.
Your Current Nodes Are Fine
Running a MeshCore repeater or companion node today works exactly as it did before the split. The dispute is over branding and trademarks — not over firmware already flashed to your hardware. No immediate action is required.
Use the Canonical Firmware Source
For new flashes or updates, download firmware from github.com/meshcore-dev/MeshCore or use the web flasher at meshcore.io. The latest release from the core team is available there. Avoid sourcing firmware from unofficial third-party sites without verifying its origin.
The Official App
The MeshCore app available on Google Play, the App Store, Windows, Mac, Linux, and the web is Liam Cottle's work — available through meshcore.io. This is the recommended app for all platforms.
Watch the Trademark
A trademark application is not a trademark grant. The application filed by Andy Kirby is still being processed. Follow updates at blog.meshcore.io. The community consensus and the legal process are separate tracks — the core team's GitHub repo remains the technical source of truth regardless of outcome.
Sources & Further Reading
Core Team Statement — "Meshcore.io – Why The Split?"
blog.meshcore.io · April 23, 2026
NodakMesh — "The MeshCore Split: What It Means for Operators"
nodakmesh.com · April 23, 2026 (updated May 14, 2026)
Andy Kirby's Video Response
Summarized by NodakMesh · May 14, 2026
MeshCore Europe — "MeshCore Splits Over Trademark, AI Code, and Team Breakdown"
April 27, 2026
Canonical GitHub Repository
github.com/meshcore-dev/MeshCore
Official Site
meshcore.io