Spare Pi 4 and touchscreen become a tap-to-approve panel for Claude

Oct 17, 2026 Last reply: 4 hours ago 4 Replies
Jump to replies (4)

When this build is running, it acts as a physical approve or deny panel for Claude desktop. A permission request shows up on the screen with the command listed, and a tap on one of the two buttons decides it. In the demo, tapping Approve once brings up a green checkmark reading Approved, and the mascot Mochi turns pink with floating hearts labeled Happy.



The maker put it together from a spare Raspberry Pi 4 and a 7-inch touchscreen that were already sitting unused, and said the project seemed like fun for exactly that reason. On the software side it runs Pi OS Trixie with Chromium in kiosk mode, starts automatically on boot, and talks to Claude by reimplementing the Hardware Buddy protocol with BlueZ and Python. Since the official Hardware Buddy gadget is an ESP32-based M5StickC Plus, rebuilding that protocol on idle parts seems like a genuinely clever reuse of hardware to me.



The details that stand out: Mochi reacts to what Claude is doing, the home screen already carries a tokens-today counter, and the dashboard shows session counts, task statuses and a working state badge. The code is MIT licensed and hosted on GitHub, and the maker is clear this is a side project rather than an Anthropic product.



There are open ends worth noting. The demo clip was recorded with demo data rather than live sessions, scheduled task support has not been tried, and how the device copes with long unattended runs on real hardware is untested so far. Testing so far was done with Claude desktop running on a Mac. Those gaps do not dim the build; they just mark where the next work sits.


Nice piece of work. I am curious about the link itself: does the Pi stay paired to the Mac over Bluetooth the whole session, or does it reconnect when a permission request comes in? The Hardware Buddy protocol angle is interesting and I would love a bit more detail on how the connection is held up in practice.

The choice to boot straight into Chromium in kiosk mode seems the smartest part of the software setup. It turns the Pi into a single-purpose panel instead of a small general computer, which fits the job perfectly. The trade-off is that the screen is locked into that one role, but for a device built around a tap decision that seems like a fair deal.

One variation worth trying: make more use of tools/notify.py, since scripts can already push a short message to the screen with it. Combined with the counters already on the home screen, that would keep the panel informative even when no permission prompt is waiting, and it needs no new hardware at all.

The maker has described the protocol side: the Hardware Buddy protocol was reimplemented using BlueZ and Python, and testing was done with Claude desktop running on a Mac. Beyond that, the pairing behaviour has not been spelled out, so whether the link stays up continuously or reconnects per request is something the maker has not said.

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required