Use case P54 · Human
Electronics hobbyist uses Claude Code to make a desk light show when his AI session is working or finished
- Electronics and 3D printing
- Advanced
- Claude Code, Arduino/PlatformIO, Adafruit NeoPixel
- Source checked · blog post
The short version
What they did
Định Nguyễn borrowed small electronics boards and used Claude to build ClauBlink, an ambient light for his home Claude Code sessions. Events from Claude Code change the light so he can step away from the terminal. The first WiFi version returned success without changing the light because two parts used different command formats. He also slowed one blinking pattern so the states could be distinguished on a single-color LED.
Result (as claimed)
“I built a physical LED indicator that shows what Claude Code is doing in real-time.”
“Slowing WORKING to 800ms made the difference obvious from across the room.”
Prompt
I want a desk light that shows what my own Claude Code session is doing. My board is [ESP32-C3 or RP2040 model], my light is [LED type], and my development tool is [Arduino IDE or PlatformIO]. Here are the board details: [attach documentation].
1. Start over USB with working, done and idle commands and clearly different light patterns, including for a single-color LED.
2. Write the firmware and a short test for sending each command by hand.
3. Once I confirm the physical light changes, add Claude Code hooks that send those same commands.Explain the setup in plain words. Keep the sender and firmware command formats identical. A success message isn’t proof the light changed; ask what I see. Send only status words, never prompts or conversation text.
Do it yourself
These steps are my suggested way in, not Định’s setup.
Level: Advanced. You flash firmware and wire hooks into Claude Code. The USB version below is the easiest start.
What you need
- Claude Code on your computer.
- A small board such as an ESP32-C3 or a Raspberry Pi Pico (RP2040), plus one LED or a NeoPixel.
- A USB cable and the free Arduino IDE or PlatformIO.
Start simple
- Ask Claude to write firmware that changes the light when it gets a one-word command over USB serial: working, done, idle.
- Flash it and send each word by hand from the serial monitor. Watch the LED, not the console.
- Ask Claude to add Claude Code hooks that send “working” when a prompt starts and “done” when it stops.
- Run a short task and step away. Check that the light changes when it should.
- If two patterns look alike, slow one down until you can tell them apart across the room.
Take it further
- Move from USB to WiFi so the light can sit anywhere in the room.
- Add a separate pattern for “needs my approval.”
- Keep one shared file that defines the commands, so the sender and the firmware can’t drift apart.
Check your work
- Treat a success message as a claim. The test passes only when the light itself changes.
- Send only status words to the device, never prompts or conversation text.
- Keep it on your own network, and don’t open the device to the internet.
Source checked. The link, author, date and quote were confirmed against the source. The result itself has not been reproduced. Prompt adapted for this library, inspired by the case. Business size: Individual. Results are quoted as the source claimed them and never improved. Spot an error or a broken link? Email charlie@cbarmorecpa.com.