What a Status Light Actually Tells You About a Claude Code Run
The Status Light is a small desk lamp with three stacked lenses, red, amber and green, that you can wire up to show, at a glance, whether a Claude Code task is still running, waiting on you, or finished. It replaces the habit of alt-tabbing back to the terminal every minute or so to check. It stands on the desk unaided, about the height of a chess piece, so it doesn't compete for room with a keyboard or a second monitor.
Why does Claude Code need something like this at all?
Claude Code tasks can run for minutes at a time, and partway through a run it may stop and ask you a question before continuing. Both of those are moments where you have, in practice, switched attention elsewhere and have no reliable cue to switch back. A light sitting in your peripheral vision removes the reason to keep glancing at the terminal window: you look up when the light changes, not on a timer you invented yourself. Unlike a screen notification, it needs nothing dismissed and nothing clicked; the state is simply there, visible from across the room, until you change what it's showing.
Does it read Claude Code's state automatically?
No, and this is the important caveat before buying one. The Status Light is hardware plus the manufacturer's utility; it does not ship knowing what Claude Code is doing. You write a small amount of glue, typically something that fires when a run starts and again when it stops or needs input, and that glue is what actually drives the lamps. The upside is that once it is wired to a start/stop signal, it doesn't care whether that signal came from Claude Code, a test suite, or a deploy script.
What should red, amber and green mean?
Whatever you decide. The three lenses are independently addressable, and a common convention maps naturally onto Claude Code's three states:
- Red, a Claude Code task is still running
- Amber, paused, waiting on your input
- Green, finished cleanly
Nothing in the hardware enforces that mapping; it is a convention worth keeping only because it is the one most people default to, which matters if you ever hand the desk to someone else.
Who shouldn't buy this yet?
If "no configuration" is a requirement rather than a nice-to-have, wait for a later revision instead of buying this one and being disappointed that it doesn't already know what Claude Code is doing. It is worth adding that a wired, USB-C version is the one we recommend; a rechargeable Bluetooth variant exists but carries a lithium cell that restricts how it can ship by air, and the wired version avoids that problem entirely along with the need to ever recharge it. It's also worth asking whether you need this at all: if most of your Claude Code tasks finish in a few seconds rather than minutes, the whole premise of a status light, protecting your attention during a wait, doesn't apply, and glancing at the terminal costs you nothing you'd notice.
If you would rather have an ambient screen than a signal light, the Desk Terminal covers similar ground with more detail than three colours can carry. Both sit under the field notes tagged Claude Code.