I use Claude Code all day, and I kept doing the same thing: alt-tabbing to the terminal to check if it had finished or was waiting for me to answer a question. So I built Claude Color, a small Windows tray app that turns Claude Code's state into light.
| Claude Code event | Color |
|---|---|
| Working | 🔵 blue |
| Asked a question | 🟡 yellow |
| Plan waiting for approval | 🟣 purple |
| Asked for permission | 🟠 orange |
| Finished | 🟢 green |
Now I can walk away from the desk. When the lamp turns orange, I know it needs me.
Claude Code has hooks: commands it runs on events like UserPromptSubmit, PreToolUse, Notification and Stop. Claude Color installs one hook entry per event in ~/.claude/settings.json (keeping any other hooks you already have):
ClaudeColor.exe hook and passes the event as JSON on stdin.PreToolUse + ExitPlanMode becomes "plan", a permission_prompt notification becomes "permission", and so on) and sends it over a named pipe to the tray app. The hook returns right away, so Claude Code never waits on the lights.
Two details make it nicer to live with:
PostToolUse hook, not by a fixed timer.Stop. Anything that happens in between shows its own color and then goes back to blue.
It's .NET 10 / Windows Forms, shipped as a single self-contained exe.
One device, one owner. If OpenRGB and the vendor software (MSI Center, iCUE, Armoury Crate) both drive the same LEDs, they fight, and some GPU LED controllers simply stop responding until you restart. The app has a troubleshooting page that checks for this, but the real fix is choosing which tool owns each device.
It's MIT licensed: https://github.com/JoaoXavierDEV/Claude-Color
Download ClaudeColor.exe from the latest release, open it, and click Install hooks. I'd love feedback, especially from people with RGB hardware I haven't tested.