Just a glance across the desk tells you what's happening.
In the quiet intervals between human intention and machine response, a developer found a way to make the waiting visible. A small open-source project called Claude Lamp translates the invisible states of an AI coding assistant into ambient light — navy for work in progress, mango for stillness, purple for a question unanswered. It is a modest but telling artifact of how humans are learning to coexist with tools that think on their own schedule.
- The frustration of not knowing whether an AI is working or stalled has become a real friction point in modern development workflows.
- A developer built an open-source fix: an LED lamp that changes color in real time based on Claude Code's status, removing the need to watch a screen.
- The project is live on GitHub and already demonstrated working, but it is tethered to a narrow set of conditions — macOS only, Bluetooth-dependent, and optimized for a single lamp model.
- Windows and Linux developers are locked out entirely, and even Moonside lamp owners outside the Halo model face uncertain compatibility.
- Because the code is open-source, the door is open for others to port it, fork it, or adapt it — the idea may travel further than the original implementation.
Anyone who has worked with Claude Code knows the peculiar limbo of waiting — staring at a screen, unsure whether the system is still thinking or has quietly stalled. A developer known as MountainSnow decided there had to be a better way, and built one.
The result is Claude Lamp, an open-source GitHub project by bobek-balinek that connects an LED lamp to Claude Code's status in real time. Navy blue signals active code generation. Sunset mango means the system is idle. Purple means it needs something from you. Instead of monitoring a screen, you glance across the desk.
The project works via macOS Bluetooth, using Apple's CoreBluetooth framework to bridge computer and lamp. It is optimized for Moonside's Halo model, with cautious documentation suggesting it may work on other Moonside lamps — the One, Aurora, and Lighthouse — though without guarantees. Other smart lamp brands are not supported.
The platform constraint is the sharpest edge: Windows and Linux users are currently excluded entirely, which puts a meaningful portion of the developer community on the outside looking in.
What gives the project staying power beyond its narrow compatibility is the idea underneath it — that development benefits from ambient feedback, from status that comes to you rather than requiring you to seek it out. And because it is open-source, it is also an open invitation: to port, to fork, to adapt. For macOS users with the right hardware, it is a genuinely useful tool. For everyone else, it is a reminder that the most practical developer tools often begin as one person solving their own problem and choosing to share the solution.
Anyone who has spent time working with Claude Code knows the peculiar limbo of waiting. You've fed the system a problem, hit enter, and now you're stuck in that familiar loop: staring at the screen, refreshing, checking back, wondering if it's still thinking or if something has stalled. A developer going by MountainSnow decided there had to be a better way—and built one.
The solution is elegantly simple: an LED lamp that talks to Claude Code and changes color to tell you what's happening. Navy blue means Claude is actively generating code. Sunset mango means it's idle, waiting for your next instruction. Purple means it needs something from you—a decision, a clarification, a nudge forward. No more monitor-watching. Just a glance across the desk.
The project lives on GitHub under the name "Claude Lamp," created by bobek-balinek. It's open-source, which means anyone with the right hardware and operating system can download the code, follow the setup guide, and build their own. MountainSnow did exactly that and posted a video of it working—the lamp cycling through its color states as Claude Code ran through its paces. The response was enough to make it worth documenting here.
But there are real constraints worth understanding upfront. The project works best with Moonside's Halo lamp, which is the model the creator optimized for. The documentation suggests it "should work" with Moonside's other models—the One, Aurora, and Lighthouse—but that's more of a hopeful note than a guarantee. If you own a different brand of smart lamp, this particular solution won't help you.
The bigger limitation is platform-specific. This runs on macOS via Bluetooth, using Apple's CoreBluetooth framework to communicate between your computer and the lamp. Windows and Linux users are currently out of the picture. That's not a small thing—it means a significant chunk of the developer community can't use this without either switching operating systems or waiting for someone to port the code to their platform.
What makes the project worth attention anyway is the underlying idea: the recognition that development workflows benefit from ambient feedback. You're not constantly checking a status; the status comes to you. It's a small quality-of-life improvement, the kind that compounds over a day of work. And because it's open-source, it's also an invitation. Someone running Windows could fork it and adapt it. Someone with a different lamp could modify the Bluetooth protocol. The foundation is there.
For macOS users with a Moonside Halo lamp and the patience to work through a setup guide, this is a genuinely useful tool. For everyone else, it's a reminder that the best developer tools often come from developers solving their own problems and sharing the solution.
Citas Notables
Sometimes you just have to let Claude cook, which usually means it's time to stand up and grab a mug of coffee.— The original project documentation
La Conversación del Hearth Otra perspectiva de la historia
Why does someone need to know what Claude is doing without looking at the screen? Isn't that what the interface is for?
Because you're not always at the screen. You step away to think, to grab coffee, to stretch. But you want to know the moment Claude finishes so you can review the code. Checking back every thirty seconds is exhausting. A lamp that tells you the state without you having to look—that's ambient awareness.
So it's really about reducing friction in the workflow.
Exactly. It's a small thing, but small things add up. You're not context-switching as much. You're not breaking your train of thought to check a monitor.
Why does it only work on macOS? Is that a technical limitation or just where the creator started?
The creator used Apple's CoreBluetooth framework, which is macOS-specific. Someone could port it to Windows or Linux, but that requires work. It's open-source, so it's possible. It just hasn't happened yet.
And the lamp compatibility issue—why is that uncertain?
The creator optimized for the Halo because that's what they had. The other Moonside models probably have similar Bluetooth protocols, but without testing, you can't be sure. It's the difference between "should work" and "will work."
Does this feel like a niche tool or something that could become more mainstream?
Right now it's niche—specific hardware, specific OS. But the idea is universal. Any developer waiting on any AI system could benefit from this. If it gets ported and becomes easier to set up, it could spread.