Meta has released ESP32 firmware and a Linux SDK for Muse, letting makers choose a screen, button or sensor before connecting a device to the agent. I support opening the interface before settling on a hardware use case. If people ultimately keep using their phones for the same task, however, the dedicated device’s value needs reassessment.Repository
Announcement coverage is dated 2026-10-02. Engadget’s Yahoo edition shows 20:27 UTC, or October 3 at 04:27 in Taipei. This article uses the previous day’s announcement within the 48-hour window, with an 08:59 Taipei cutoff. Official pages give no activation time; publication does not establish it.Report Announcement date
The released code connects hardware to Muse rather than putting the whole agent on the chip. Devices need a token and pair through the Muse mobile app, giving the agent different input and output interfaces. Losing connectivity or access to the service cannot be remedied by possessing the open code alone.Pairing
Meta’s Home Link provides a concrete example: it connects compatible devices or local HTTP APIs over home Wi-Fi so Muse can control them. Nat Friedman says 5,000 units have been made. The official site schedules shipping for October, free to US subscribers and limited to one per person. Manufactured units are not delivered units or active users, and compatibility does not extend automatically to every appliance.Home Link Quantity
Separate reporting describes Federico Viticci turning an Xteink e-reader into a Muse display attached to his phone, with the agent loading content onto it. This homemade example shows information leaving the chat window. It does not provide comparative evidence on sustained use, update latency or battery life.Maker example
Where a device sits is a product decision
Suppose a schedule summary stays visible somewhere a person passes on the way out. They might avoid unlocking a phone and locating the conversation. That benefit comes from information appearing where it is needed; it need not depend on the model producing smarter answers. Put the same summary on a rarely visited desk, and it may simply add another device to charge and maintain.
This is why I favor the opportunity to compare interfaces that the release creates. Existing components can help establish which information deserves a persistent display before someone commits to a dedicated enclosure or extra buttons. That leaves more room for adjustment than betting on one hardware shape at the outset. This is a product-design inference: sample code does not establish market demand or settle questions about habits that have not been measured.
Open examples also allow hardware changes and agent updates to proceed separately. Yet someone reading a summary usually cannot tell from its content whether the connection has just failed. For a persistent display, I would retain a last-updated time and an offline indicator so yesterday’s information does not look like today’s reminder. That recommendation follows from the connectivity dependency; it is not an officially demonstrated reliability result.
Code licensing and service access are separate
The repository uses Apache-2.0, but SDK tokens have separate personal, non-commercial terms. Meta can revoke tokens and does not promise support. Permission to modify the code does not authorize selling devices that use those tokens. The free Home Link offer is limited to the US; it does not establish equivalent availability in Taiwan.Code license Service terms Availability
I therefore regard this release as a tool for exploring interactions, not yet a commercial device platform to rely on. For someone manufacturing a product, continued service access and how failures appear to users affect responsibilities after delivery. Available information does not supply enough cost or availability data to estimate long-term spending per device.
Home Link delivery volumes can test the fulfillment plan. Whether people keep using a dedicated device, and how often they still return to their phones, can test the interface’s usefulness. These are different questions. Public code and reference connections are available now; whether the hardware becomes a daily habit requires evidence from subsequent use.
The cover reuses this site’s Muse Code brand illustration, not a photograph of Muse Gadgets. Event-image downloads failed because domain names could not be resolved.
Sources: