A light that says the work is finished and a computer that can change files may both be called gadgets. They give an assistant very different reach. Start with that difference before choosing a board for Meta’s Muse Gadget SDK.
Meta publishes the Muse Gadget SDK for connecting supported ESP32 and Linux devices to its hosted agent. The October 2 account in The Verge introduced the release. The useful question for a project is what the connection should allow the agent to observe or do.
A gadget is an interface and an access path. It can put an answer somewhere useful, expose a local service or give the agent commands on another machine. Those possibilities deserve separate decisions.
Choose the action before the hardware
The Muse gadget project offers firmware for supported ESP32 boards and software for Linux , including Raspberry Pi computers. The DIY routes require an SDK token and pairing with the Muse phone app.
| Route | What to check first | The important access question |
|---|---|---|
| DIY ESP32 board | Supported board, firmware and interface features | What can this board receive, display or expose? |
| Linux or Raspberry Pi | Supported system, Bluetooth LE pairing and runtime account | Which commands and files can that account reach? |
| Finished Home Link | Official product setup and compatible network services | Which local services become available? |
The table is a way to choose a route, rather than a claim that all three offer the same tools. A light and button can suit a small status project. A computer account can support much broader actions.
Seeed ’s reTerminal E1001 e-paper display offers another kind of interface: information placed where someone will encounter it. That placement may make a reminder easier to notice without changing the model that produced it. Check the project’s support list for the exact board and firmware before buying or flashing hardware.
Follow the matching setup path
The official ESP32 instructions identify the ESP32-C5 DevKitC-1 as a simple starting point with a light and BOOT button. A manual build needs a data-capable USB cable, a macOS or Linux computer and the toolchain specified by the current quickstart. Review the SDK terms and obtain the token before pairing.
The Linux SDK instructions list supported systems and Bluetooth LE requirements. Raspberry Pi options include 3B+, 4, 5 and Zero 2 W. Installation needs administrative access, but the account selected for the agent’s commands can be more limited.
For either DIY route, follow its own sequence:
- Confirm the exact device and current prerequisites in the matching quickstart.
- Prepare the firmware or review the Linux installer, including the runtime account.
- Configure the SDK token through the documented path.
- Enable developer mode under Devices in the phone app, add the gadget and complete its confirmation steps.
- Check the connection with the device’s status indication or documented service checks before assigning work.
These are documented setup paths, rather than a firsthand installation test. Firmware versions and supported features can change. Keep the maintained instructions beside the hardware instead of combining steps from different devices.
Home Link is a finished-device route
Muse Home Link is a USB-C device based on ESP32-C5. Its stated role is to reach compatible home-network services, including local HTTP interfaces. The product page limits its offer to active Muse subscribers in the United States, one per subscriber, and says it runs official firmware that cannot be reflashed.
That makes it a different choice from a development board intended for custom firmware. A finished bridge may fit the job. A build-your-own project may require something else. Use current product availability and setup information rather than treating the original October shipping wording as a present delivery promise.
Compatibility also belongs to the service, not just the connector. A device being on the home network does not automatically establish that Muse can control it. Identify the particular interface and supported integration the project will use.
Device software does not put the model on the board
The repository publishes the SDK under Apache 2.0 , with listed exceptions for included components and avatar assets. That describes the device software. It does not make the hosted model a local model or give the service the same license.
The separate Muse Spark Open setup on two Mac Studios shows the different demands of hosting a large model. Pairing a display to a service solves another problem.
This distinction matters when a connection fails. Information already shown on a display can look just as convincing as a fresh response. In a briefing project, give the information a timestamp and a recognizable connection state. Yesterday’s answer should be easy to distinguish from today’s.
The same care applies to audio. Supported microphones, speakers and firmware paths vary by board. Their presence on a hardware specification is not enough to establish the interaction the finished project will provide.
Linux grants a different kind of authority
The Linux SDK exposes shell execution, file reading and writing, and health information. Commands run with the selected account’s permissions. If that account can use sudo, the agent can use that capability too.
Consider a hypothetical backup-status project. The first task is to observe a status record and report it. Repairing the backup, changing configuration and deleting files are additional actions. Naming the first task clearly makes it easier to notice when the proposed access reaches further.
The Mac permissions guide follows the related distinction between a task and the system access behind it. A small device does not necessarily imply small authority.
Pairing adds another distinction. The documentation describes physical confirmation and encrypted sessions, while stating that community devices lack manufacturer verification. Access to the hardware, protection of a session and verified device identity answer different questions.
Before building, finish one sentence: this device should receive this input and be allowed to produce this result. A status light, a network bridge and a shell executor may each be useful. The clearer that sentence, the easier it becomes to choose the one that fits.
FAQ
Does the Muse Gadget SDK run the hosted model on an ESP32 board?
No. The device SDK connects supported hardware to the hosted agent. Pairing a gadget is different from hosting the model locally.
Can ESP32 and Linux gadgets do the same things?
Their supported tools differ. ESP32 features vary by board and firmware. The Linux route can run commands and access files with its selected account’s permissions.
What do DIY gadgets need before pairing?
They need supported hardware and software, an SDK token and the Muse phone app. Follow the matching quickstart for prerequisites and confirmation steps.

