Muse Gadgets is Meta’s 2 October 2026 release of open-source device software for people who want to connect its Muse agent to physical controls and displays. The official project offers an ESP32 device SDK and a Linux device SDK for computers such as Raspberry Pi. The code is open, but access to the Muse service still needs a Meta-issued token whose terms restrict commercial use.
Key takeaways
- Meta published ESP32 and Linux gadget code in its official GitHub repository under Apache 2.0, with listed exceptions for third-party files.
- The official Muse Gadgets site presents hobbyist project ideas, developer instructions and a separate Muse Home Link device.
- SDK token terms currently limit token use to personal, non-commercial projects and tightly restrict sharing or selling token-enabled devices.
- The Home Link offer is for eligible Muse subscribers in the United States. Joining its queue holds a place; it does not complete an order.
That separation between software license and service access is the key business story. A developer may study and modify the published code. That does not automatically grant permission to sell a gadget connected to Muse or build a supported commercial product around the agent. Meta calls the SDK experimental and says access can change or end. For an Indian maker or startup, those terms matter more than the attractive images of small screens and buttons.
What did Meta release with Muse Gadgets on October 2?
Meta’s project README divides the release into two paths. One connects an ESP32 board to Muse and can add a screen, audio or sensors. The other turns a Raspberry Pi or another supported Linux computer into a gadget. Devices pair through the Muse app, after its developer mode is enabled. A gadget needs a token to pair. These are published instructions, not evidence that every board or accessory will work with every version of the app.
The official site shows examples including a circular screen, an e-ink display, a small status display and a possible HDMI stick. Some are products made by other companies; Meta expressly says it does not endorse or warrant those third-party devices. The site calls the hardware work a tinkering project. That positioning is important because the name “Muse Gadgets” could be mistaken for a new mass-market line of products manufactured by Meta. Most examples are ideas or existing boards supplied by others.
Independent coverage helps date and bound the event. TechCrunch reported the launch on October 2. ITmedia’s October 3 report examined the two SDKs and Home Link offer. Aree Blog’s technical account checked the repository and token restrictions, including the difference between local hardware and Meta’s cloud agent. These are distinct publisher accounts; the GitHub repository, project site and token terms remain the primary sources for product specifics.
What does open source mean here?
The repository states that its device SDKs and firmware use the Apache 2.0 license, apart from identified third-party components governed by their own licenses. This means developers can inspect, modify and reuse the released code under that license’s conditions. It does not mean Meta has open-sourced the Muse agent itself, the user’s account, the cloud service or its infrastructure. Hardware at home remains an interface to a service controlled elsewhere.
Nor does an open code license override the terms for the token required to pair a device. Meta’s Gadget SDK Token Terms say the token is for personal, non-commercial use with a user’s own account. A token may be embedded in no more than 50 devices shared with others, and it may be linked to no more than 50 devices in total. The terms prohibit using that token in a device sold for payment or offered through a marketplace, promotion or reward without Meta’s prior written permission. A developer could legally reuse Apache-licensed source in one context yet still lack permission to connect a commercial product to Muse. Those are separate rights.
The terms also say the SDK and token are provided as available, rather than as a supported developer platform. Meta may suspend a token in specified circumstances. Anyone designing a business around this project should read the current terms directly, seek authorization for commercial distribution and plan for changes in service availability. An article that calls Muse Gadgets an open commercial hardware platform would misstate the current product.
Which devices can Muse Gadgets developers use?
The ESP32 route is aimed at small, inexpensive microcontroller boards. An experiment might use a button to send a prompt, a display to show an answer or a sensor to supply context. But the supported interfaces depend on the chosen board, firmware configuration and published examples. Meta’s site lists particular third-party boards and display products. It does not promise universal compatibility with every inexpensive ESP32 device.
The Linux route has a different risk profile. A Raspberry Pi can run more general software and access a wider range of files or home-network services than a small microcontroller. Meta presents Home Assistant as one possible integration. That makes the Linux SDK interesting for experienced makers, but it also raises questions about what an agent should be allowed to do on the machine. The user’s own device permissions and the SDK configuration determine the exposure. A reader should not assume that pairing a Pi is equivalent to pairing a simple status light.
Projects displayed on the Muse site are examples, not products that have all shipped. The HDMI stick is labelled as coming soon. Other illustrated hardware comes from third parties. Similarly, a consumer should not mistake a conceptual gadget description for a tested recommendation, warranty or product review. The practical starting point is the repo’s current hardware list and setup guidance, then an assessment of token and account permissions before connecting anything sensitive.
What is Muse Home Link?
Meta also presents Muse Home Link, its own USB-C-powered device for connecting Muse to compatible devices on a home Wi-Fi network or to local HTTP APIs. The project site says community-built skills may, depending on setup, help an agent control a light, television or printer. Those examples indicate possible uses; they do not mean any such device will automatically work in every home.
Meta’s site says Home Link is free for an active Muse subscriber in the United States, limited to one per subscriber, with October shipping planned on a first-come basis. Its claim interface describes joining a line, not completing an order. TechCrunch reported that Meta had made 5,000 units, citing product leader Nat Friedman. That reported number should be attributed to the company executive and is not a promise that units remain available now. The official claim page is the current source for eligibility and status.
The original Lapaas Voice story described Home Link as a universal, zero-configuration gateway and suggested a guaranteed free allocation. The official material is narrower. A Home Link can reach compatible local devices when properly configured. A queue position depends on a Muse account and eligibility. We have removed claims about effortless pairing, universal device control and an assured shipment.
How do Muse Gadgets differ from Muse Charm and Small Business?
These launches share a Muse name but answer different product questions. Muse Charm is a Meta-designed pocket device announced at Connect. It is a consumer product with its own target shipping window. Muse Gadgets is open device software and examples for people building their own interfaces. Muse for Small Business is a separate offering announced on 29 September for running business tasks. The gadget token’s non-commercial restrictions should not be confused with the terms for that business product.
This article therefore covers a distinct October 2 developer release, not a second telling of the September 29 small-business announcement. The connection is strategic: Meta is testing several ways to extend Muse beyond a chat interface. But the eligibility, commercial rights and delivery status differ across products. Treating them as one launch would make the product and policy story less accurate.
What does an Indian maker need to know?
The code is visible globally, but the product ecosystem has limits. The Home Link free offer described on the site is United States-only. The SDK uses a Muse account and Meta-issued token. A maker in India can study the repository and its license, yet should check whether account access and pairing are available in their region before buying components for a build. Public documentation is a better basis than assuming that open source means worldwide service access.
For a small hardware company, the strongest warning is contractual. The current token terms do not permit selling token-enabled gadgets as an ordinary commercial product. A 50-device sharing cap is not a commercial manufacturing allowance. It is a limit inside a personal-use scheme. Anyone considering a market launch needs direct written permission from Meta, a supported commercial integration route or a design that does not depend on that restricted token.
Privacy also deserves attention. The official token terms limit access to one’s own Muse account and prohibit collecting another person’s Muse data outside narrow, disclosed device functions. An e-ink dashboard displaying private summaries, for example, presents a very different privacy problem from a button that starts a low-stakes prompt. Physical interfaces often expose information to whoever is nearby. Product builders need to consider display visibility, pairing, token storage, revocation and the household context before calling a gadget safe.
What should readers watch next?
- Documentation: Does Meta expand the published board examples and clearly explain permissions for Linux devices?
- Service terms: Will there be a commercial SDK or written pathway for companies that want to sell hardware?
- Availability: Which countries can create Muse accounts and pair a gadget, and when does Home Link actually ship?
- Support: Does this remain a hobby project, or does Meta publish stability and support commitments?
- Community evidence: Do independent builders demonstrate useful, reproducible projects instead of concepts alone?
The Muse Gadgets code release is real, dated and inspectable. Its significance will depend on how many people can use the service responsibly and whether Meta opens a viable route beyond personal experiments. Until then, Muse Gadgets is best described as an open-source device toolkit connected to a closed, token-governed agent service.
Frequently asked questions
Is the Muse agent itself open source?
No. Meta released device SDKs and firmware. The agent service remains separate and requires a Muse account and token.
Can someone sell a gadget built with this SDK?
The code license permits reuse under its conditions, but the current Gadget SDK token terms prohibit selling or publicly listing a device that embeds the token without Meta’s prior written permission.
Is Muse Home Link free in India?
Meta’s current claim page limits the free Home Link offer to eligible Muse subscribers in the United States. It does not announce an India offer.
Is the HDMI stick available now?
The official project site labels that example as coming soon. Readers should not treat it as a shipped accessory.
Correction note, 4 October 2026: This article was rewritten against Meta’s repository, project site and token terms. An earlier version included an unattributed third-party image and unsupported claims about protocols, costs, example builds, seamless setup and commercial use. Those claims and the image have been removed. The 5,000-unit Home Link figure is now attributed to reporting that cites Meta’s product leader.
Get the day’s top stories in your inbox
One concise email. No spam, unsubscribe anytime.
