What is Meta Muse Gadgets? What can physical AI devices do?

What is Meta Muse Gadgets?

Meta’s open-source Muse Gadgets SDK is a toolkit for building AI devices. Its repository includes SDK code for ESP32-based devices and Linux, with examples for displays, buttons, sensors, speakers, and other peripherals. A separate HomeLink path explores smart-home interactions. The shared idea is to connect an agent to physical inputs and outputs, not only a chat window.

Muse gives developers a starting point for prototyping embodied AI. The board, peripherals, and finished experience depend on what each builder puts together.

Each peripheral can play a different role: a button can capture a simple input, a sensor can provide local context, and e-paper or a speaker can return a brief result. The useful design question is which signal belongs at the work surface. A small glanceable cue helps when an agent is working in the background and the person stays focused on another task.

What can physical AI do at your desk?

Imagine asking Claude desktop to edit a file while you review another task. InksPet reflects agent activity on EleksCava’s e-paper display: the pixel crab moves, RGB lights show the working state, and a concise status stays in view. You can keep your main screen on the work in front of you.

When a supported Claude desktop Hardware Buddy action needs approval, the light pulses yellow and the device shows the request. Press A to allow, B to always allow, or C to deny. After approval, task activity shows green; when it finishes, InksPet shows Completed with a green fade. You can follow the workflow at your desk instead of searching for a hidden dialog.

The e-paper screen keeps useful context nearby, while a glance at the lights tells you when the state changes. For Codex, InksPet’s documented local bridge sends supported hook status to the device. The physical approval sequence above applies to supported Claude desktop Hardware Buddy requests; controls depend on each integration.

That short loop matters during a longer code edit: notice the request before the agent pauses, answer it from the device, then see task progress and completion. The e-paper holds enough context to decide whether to wait or act, and the completion signal closes the loop without pulling you back to a dashboard.

The 2.9-inch, 296 × 128 e-paper display leaves room for a short task summary, while five RGB LEDs make state changes visible and three physical buttons handle supported responses. It is a glanceable status surface beside the keyboard, designed to complement the editor and chat rather than replace them.

InksPet and Muse are separate

InksPet firmware runs on EleksCava e-paper hardware. The current product documents a native Claude desktop Hardware Buddy connection and a local Codex bridge. InksPet has not been validated against the Muse SDK, so choose it for those documented paths; they do not require a Muse account or token.

For developers exploring Muse, the current SDK terms limit SDK Tokens to individual, non-commercial use and prohibit embedding them in products offered for sale or promotion.

Try it on your desk

If you already own an EleksCava device, install InksPet through the browser-based firmware installer, then follow the setup guide (English). It explains device setup and supported integrations.

If you are shopping for hardware, visit EleksCava’s AI Companion page for current product and purchase details. EleksCava supplies the device; InksPet is the firmware that adds the pixel-crab agent companion. Check the product page for the current configuration and what is included.

Muse puts a wider idea in the spotlight: AI interfaces can include a display, light, or button in the room. InksPet is one way to try that today with an existing desk device.