Meet the Claude Desktop Buddy: A BLE‑Powered Hardware Pet That Handles Code Approvals

What It Is

Claude Code requires frequent manual approvals for actions such as running a bash command or deleting a file, which interrupts a developer’s focus. Anthropic’s solution is to expose the approval flow over Bluetooth so that a physical device can handle the interaction.

Technical Mechanism

The open‑source claude-desktop-buddy project uses the Nordic UART Service (NUS) over BLE, a widely supported serial‑over‑Bluetooth protocol for Arduino, ESP32, nRF52, and Raspberry Pi. The desktop client continuously sends newline‑delimited JSON heartbeat packets that report session counts, pending approvals, recent commands, and token usage.

{"total":3,"running":1,"waiting":1,"msg":"approve: Bash","entries":["10:42 git push","10:41 yarn test"],"tokens":184502,"tokens_today":31200,"prompt":{"id":"req_abc123","tool":"Bash","hint":"rm -rf /tmp/foo"}}

The presence of the prompt field indicates an operation awaiting approval. The hardware replies with a JSON command to grant or deny the request:

{"cmd":"permission","id":"req_abc123","decision":"once"}

Beyond approvals, the protocol supports dragging local folders to the device (e.g., for firmware updates) and sending events after each conversation. All details are in the public REFERENCE.md, and the API is only enabled in Developer Mode, explicitly marked as experimental for makers.

Community Weekend Activity

Within a weekend, developers ported the buddy to several form factors:

Round‑screen ESP32, enabling approval directly on a small display.

X‑Knob, a rotary encoder device that provides tactile feedback and turns approval into a physical twist and press.

M5Stack Cardputer with a QWERTY keyboard.

Raspberry Pi Pico W, demonstrating that the protocol is simple enough for rapid weekend integration.

Why It Matters

The API does more than externalize a button; it turns Claude Code’s runtime state into a subscribable data stream. Heartbeat packets expose token consumption, session count, and current commands, enabling novel hardware behaviors:

Physical state sensing : LED brightness or motor speed can reflect token usage.

Offline approval : Approve actions from another room without a computer.

Biometric gating : A fingerprint module can require a biometric match before permitting sensitive commands.

Physical emergency stop : A red hardware button can instantly abort dangerous operations.

Context awareness : An IMU can detect when the device is lifted and only allow approvals while held, preventing hidden attacks.

Potential Business Directions

The open API opens several entrepreneurial avenues:

Claude‑specific peripherals : A polished, battery‑powered device priced $99–$200 for power users.

Unified AI‑tool control panel : A protocol layer that aggregates status from Claude, Cursor, Copilot, etc., similar to a Stream Deck.

Enterprise‑grade audit hardware : A tamper‑evident device that logs every command, requires biometric approval, and stores immutable audit trails.

Maker‑focused education kits : Curriculum and hardware bundles that teach embedded development through Claude‑driven projects.

Anthropic describes the API as “for makers,” indicating they do not plan to produce commercial peripherals themselves, leaving the space open for community‑driven innovation.

References

claude-desktop-buddy GitHub repository: https://github.com/anthropics/claude-desktop-buddy

BLE protocol documentation (REFERENCE.md): https://github.com/anthropics/claude-desktop-buddy/blob/main/REFERENCE.md

Felix Rieseberg’s announcement tweet (2026‑04‑17): https://x.com/felixrieseberg/status/2044920611215233397