Meta is opening two routes for Muse to interact with hardware: programmable gadgets built with its open-source SDKs, and a Home Link device that connects the AI agent to compatible equipment on a home network.
DIY builders can adapt the released code for ESP32 boards or Raspberry Pi/Linux systems, adding displays, buttons, audio, sensors, and controls. Home Link offers a ready-made network bridge, but it runs only official firmware and cannot be reflashed.
The Muse Gadgets project gives developers a way to extend Muse beyond its app. It also raises practical questions about permissions, device compatibility, and community-written instructions that can trigger actions on a local network. Before building or connecting anything, it helps to separate what Meta provides from what remains the builder’s responsibility.
What Builders Can Make With the Muse SDKs
Meta’s release includes an ESP32 Device SDK for microcontroller-based projects and a Linux Device SDK for Raspberry Pi or other Linux systems.
The ESP32 route supports projects with screens, audio input and output, and other connected sensors. Meta’s examples include a small status display, a push-to-talk device with a microphone and speaker, and a color e-ink display for briefings, reminders, or shopping lists.
These are project ideas and starting points, not finished Meta products. The site explicitly says the featured third-party devices are made and sold by other companies and that Meta does not endorse or warrant them. The TV-connected HDMI stick is also marked “coming soon,” so its appearance alongside existing hardware examples should not be read as availability.
With the Linux SDK, builders can add custom commands so Muse can handle system-administration tasks or work with a Home Assistant setup. Meta describes these uses as options for customization. A spare Raspberry Pi could serve as both an interface and a host for custom actions, though which actions work depends on what the builder implements.
The official Muse Gadget SDK repository contains the ESP32 and Linux code, firmware, and a skills directory. The main release uses Apache-2.0, with licensing exceptions for some third-party files, dependencies, and assets. Anyone redistributing a build should check those exceptions before assuming the entire project has the same license.
Meta provides the SDKs and firmware as-is, without warranty. Builders can inspect and modify the open-source device-side code, but Muse itself is not open source, and connecting to the service remains subject to separate conditions.
