Meta Opens Muse Smart Glasses to Third-Party Hardware

Meta's Muse Gadgets release is less a product launch than an infrastructure handoff. The company published its ESP32 firmware and Linux SDK as open source under an Apache 2.0 license, organizing the repository into esp32, linux, and skills directories, each carrying both a human-readable README and an AGENTS.md file explicitly written for coding agents rather than people ^[1]. That detail matters: Meta is betting hobbyists will increasingly delegate the actual wiring and firmware work to an AI coding assistant, with the SDK built to be legible to a bot as much as a person. Developers get started by grabbing a capped API token from gadgets.muse.ai - each token limited to a set number of devices - and pointing that coding agent at the GitHub repo, a workflow pitched as frictionless rather than enterprise-grade ^[2]. Alongside the open framework, Meta shipped its own reference device, Muse Home Link, a USB-C powered dongle built on Espressif's ESP32-C5 chip that lets Muse talk to TVs, speakers, and anything else exposing a local network interface ^[3]. By releasing both the open-source SDK and a working first-party example, Muse Home Link, on the same day, Meta paired the developer toolkit with proof that the approach works outside the lab.

Read past the hacker-friendly framing and the terms are strikingly one-sided. Meta states plainly that the SDK and tokens are 'not a supported product or developer platform,' and it reserves the right to change or withdraw access at any time ^[4]. Anyone who solders together a custom Muse Gadget is also on their own if the board gets bricked - Meta assigns that risk entirely to the builder ^[4]. This is a meaningfully different posture from a true developer platform with API stability guarantees and support channels; it is closer to a reproducible tech demo. The repository's own description leans into that framing, calling the project something 'built by hackers, for hackers, just for fun' rather than a foundation for commercial products ^[1]. For hobbyists tinkering over a weekend, that is a fair trade. For anyone weighing a serious investment of time or money building a business on top of Muse Gadgets, it is a flashing warning sign that the ground could shift without notice.

Muse Gadgets does not exist in isolation - it is one more hardware surface Meta has rolled out for its personal AI agent in under a month, following Muse's own launch, the Muse Charm keychain device, and glasses integration unveiled at Meta Connect. That cadence has coincided with a sharp run in Meta's stock, which rose roughly 36 percent in September 2026 amid the Muse launch cycle ^[5]. But not every analyst is convinced the hardware blitz translates into near-term revenue. Needham's Laura Martin has warned that Meta is 'notoriously slow' to monetize new products and pointedly noted that Meta does not control the endpoints that Muse needs to succeed ^[6]- a reference to episodes like Amazon blocking Muse from shopping on Amazon.com just weeks before Muse Gadgets shipped ^[7]. Giving away free hardware and open SDKs is a classic way to grow a user base fast, but it does nothing to resolve the structural problem that the platforms Muse most needs to act on - retailers, home-device makers, app ecosystems - are under no obligation to let it in.

Reaction across builder and social channels splits by which device is being discussed. On the Muse Gadgets announcement itself, Reddit's r/MuseAgent showed genuine builder enthusiasm, with commenters in the announcement thread confirming its authenticity and noting the Home Link giveaway is US-only. Sentiment on X was similarly positive, with builders framing the release as Meta building a hardware developer ecosystem for the physical world. That enthusiasm is separate from a harder-edged debate specific to Meta's earlier Muse Charm keychain device: on a different Reddit thread about Charm, skeptics described it as hype-driven device sprawl, while others countered that most of what Charm does could already be handled by binding a phone's existing action button to Muse. The two conversations should not be conflated - the Charm skepticism was about Charm, not about the Muse Gadgets SDK or Home Link, which drew builder enthusiasm on its own announcement thread.