Work · Community report
Prototype a desktop agent gadget
@Ayoubka_ says they built a small desktop AI gadget with Muse that talks back and finds flights, and @harshacharya reports Muse writing a board port and flashing muse-gadget-sdk firmware onto an unsupported ESP32-S3 screen in an afternoon. This page shows how to prototype a desktop agent gadget with the microphone and account access checked.
What you can get
- Prepare
A simple desktop interaction goal
- Ask and review
Decide the first job: talk and answer only, with no account actions yet.
- Check the result
A small desktop interaction prototype and a privacy/access checklist, not an unverified flight-booking appliance.
The source case
@Ayoubka_ says they built a small desktop AI gadget using Muse, describes it as talking back and finding flights, and links to a demonstration. The source also makes an open-source announcement claim, which this guide does not verify. The capture supports an attributed gadget-building report, not a working flight-search result or an official hardware design. @jerrod_lew says Muse helped choose a device and guided installation, after which the author could speak to Muse by tapping it; this is a separate user report, not validation of the other gadget’s design. @harshacharya reports Muse writing a custom board port (display, touch, speaker, dual-mic audio) and flashing a muse-gadget-sdk firmware build onto an unsupported Waveshare ESP32-S3 touch LCD, booting to the Muse pairing screen in one afternoon. The post does not show the code or confirm the hardware held up beyond that session. Checked on 2026-10-09.
A public report by someone outside this library. Not independently reproduced here.
From the source
Source excerpt
I built my own little AI gadget lives on my desktop, talks back, finds me flights
Source excerpt
My Muse helped me to find a device to buy and I followed it's guidance to install it here. Now can I speak directly to my Muse by tapping on it!
Source excerpt
Unboxed a Waveshare 1.85" ESP32-S3 touch LCD - not on Meta's supported gadget list. My muse wrote the custom board port (display, touch, speaker + dual-mic audio); we built and flashed the muse-gadget-sdk firmware. Booted straight to the Muse pairing screen. One afternoon, DIY voice gadget. @Muse @alexandr_wang
Quoted from the original posts. Not written by this guide, and not a result produced here.
Suggested prompt
Bring A simple desktop interaction goal, Hardware and software you are authorized to use, Microphone, network and data-retention permissions. Source community report, checked 2026-10-09.
Written by this guide as a starting point, not quoted from the source. Your edits stay in this browser.
What you need
You supply
- A simple desktop interaction goal
- Hardware and software you are authorized to use
- Microphone, network and data-retention permissions
How to try it
Editorial, not from the source
- Decide the first job: talk and answer only, with no account actions yet.
- Choose hardware. A board on the supported list is the short path; an unsupported one needs a custom port for display, touch, speaker and microphones.
- Get the firmware from the project's own repository and read its licence before installing.
- Back up or note the board's original firmware, then build and flash, and confirm it reaches the pairing screen.
- Test how listening starts and stops (tap or wake word), what the indicator shows and where audio goes.
- Add account actions such as flight search last, with a confirmation before anything is booked or sent.
Three builds, three levels of detail
@Ayoubka_ says Meta open-sourced Muse the week before, so they built their own little AI gadget that lives on their desktop, talks back and finds them flights, with a warning not to poke it too much and a link to try it. This guide has not verified the open-source claim or opened the demo. @jerrod_lew says Muse helped them find a device to buy, they followed its guidance to install it, and they can now speak to Muse by tapping on it.
@harshacharya gives the most detail. They unboxed a Waveshare 1.85" ESP32-S3 touch LCD that is not on Meta's supported gadget list; their Muse wrote the custom board port for display, touch, speaker and dual-mic audio, and they built and flashed the muse-gadget-sdk firmware. It booted straight to the Muse pairing screen, in one afternoon. Reaching the pairing screen is the milestone reported; the post does not say how voice worked afterwards.
Supported board or custom port
A board on the supported list should come with a known pin map and audio setup. An unsupported board means describing its hardware to the agent: the display driver chip, the touch controller, the audio codec or amplifier, and which pins each uses. Get these from the board maker's wiki or schematic and give them to the agent, rather than letting it guess, because a wrong pin number usually shows up as a blank screen or silent speaker rather than an error.
ESP32-S3 boards are normally flashed over USB. If the computer does not see the board, the usual fixes are a data-capable cable and holding the BOOT button while pressing RESET to enter download mode. Keep a known-good image so you can recover a board that will not boot.
A microphone on your desk
Tap-to-talk, as in @jerrod_lew's setup, is easier to trust than an always-listening device. Whichever you choose, check that there is a visible sign when it is listening, find out whether audio is processed on the device or sent elsewhere, and know how to mute it.
Finding flights is a search; booking is a purchase. Keep anything that spends money, sends messages or changes accounts behind a confirmation on a screen you can read, and give the gadget an obvious off switch.
Open Muse to try it. That is the product's own site; this guide is not part of it.
Limits and confirmation points
Limits to confirm
- Hardware, code, installation method, audio handling and the linked demonstration are absent.
- No flight-search output, booking or verified licensing terms are supplied.
- This is an attributed community report, not reproduced by this guide. The suggested workflow and checks are editorial guidance, not a recovered conversation or guaranteed product capability.
- @jerrod_lew's report does not give the hardware model, setup instructions, permissions or tap-to-talk reliability.
If it goes wrong
Editorial, not from the source
- The screen stays blank after flashing
- Check the display driver and pin map in the board port against the maker's schematic, then reflash. Keep a known-good image to fall back to.
- The computer does not detect the board
- Try a data-capable USB cable and enter download mode by holding BOOT while pressing RESET.
- It reaches the pairing screen but voice does not work
- Test the speaker and each microphone separately, and check the audio pins and mic count in the port configuration.
Common questions
Can I build a Muse gadget on a board that is not officially supported?
@harshacharya reports doing it with a Waveshare ESP32-S3 touch LCD, with Muse writing the board port, and reaching the pairing screen in an afternoon. This guide has not reproduced it.
Do I need to write the firmware myself?
In the reports, Muse wrote the port or gave installation guidance, but you still build, flash and wire things yourself. Neither post says how much the authors already knew.
Is Muse open source?
@Ayoubka_ says Meta open-sourced it; this guide has not verified that. Check the actual repository and licence of any firmware before installing it.
Can the gadget book flights?
@Ayoubka_ says it finds flights. No search output is shown and no booking is claimed. Keep purchases behind your own confirmation.
Next
More in Work
Similar tasks
Get recurring task recommendations — ask your own agent to check for relevant updates.