Show status or images on a screen
Choose an ESP32 board whose official feature table lists the display and image support your task needs.
Compare boardsChoose a path
Meta’s Muse Gadgets: ESP32 vs Linux
Short answer
Choose the ESP32 path for a supported board with the display, buttons and voice features you need. Choose Linux or Raspberry Pi when Muse needs to run commands, read or write files, or work with computer-connected tools. Both connect to Meta’s Muse and need an SDK token; their capabilities and permissions differ.
Pick by task
Build a push-to-talk handheld
Choose a supported ESP32 board with push-to-talk. Voice sessions and text replies differ across boards.
Find push-to-talk boardsLet Muse run commands and move files
Choose Linux. Muse uses the permissions of the account selected during installation.
Linux requirementsSide by side
| Criterion | ESP32 board | Linux or Raspberry Pi | Sources |
|---|---|---|---|
| Hardware | An ESP32-compatible board; features depend on the board. | Raspberry Pi 3B+, 4, 5 or Zero 2 W, or a Linux computer with Bluetooth LE. | |
| Host and operating system | A macOS or Linux computer builds and flashes the board. | Raspberry Pi OS Bullseye+, Debian 11+ or Ubuntu 22.04+; 32-bit and 64-bit systems. | |
| Installation | Build firmware with ESP-IDF 6.0.1, then flash over a USB serial connection. | Run the Linux installer; it installs under /opt/musegadget and starts a service. | |
| SDK token | Each gadget needs an SDK token; enter it in the firmware build configuration. | Each gadget needs an SDK token, supplied to the installer. | |
| Pairing | Enable Developer mode in the Muse app and add the flashed device; the BOOT button confirms setup. | Enable Developer mode and add the device when Bluetooth pairing opens. | |
| Network | Connects the board to home Wi-Fi. The home-network tunnel depends on board memory. | The Linux computer is already on its network before pairing. | |
| Commands and access | Board firmware exposes supported gadget features and, on supported boards, a tunnel to local HTTP APIs. | system.run, file.read, file.write and device.health run with the installation account permissions. | |
| Extending the device | Add displays, buttons or support for another board in the firmware. | Add executor commands, wire sensors or bridge events into a Muse chat. | |
| Keeping the connection | Reflashing keeps pairing and Wi-Fi settings; erasing flash starts fresh. | The service stays connected across reboots; pairing can be reopened with musegadget pair. |
One difference matters most
The Linux gadget runs commands as the account selected during installation. If that account can use sudo, Muse can too. The official installer documents how to select a different run-as account.