I use Claude Code all day, and I kept losing track of what it was actually doing. It'd go heads-down for two minutes firing tools and burning context, and the terminal showed me everything except what I cared about. Which tools did it just run? How full is the context window?
I ended up with a usage CLI in one tab, a cost tool in another, and a statusline I had to squint at. I didn't want three side-tools. I wanted one surface to glance at. A cockpit.
So I built Conan, a native macOS app that sits beside Claude Code and turns its live session into a HUD:
- a streaming timeline of every prompt, tool call, and skill as it fires - a context-window gauge you watch fill - a usage and cost pulse
It reads Claude Code's local data. No telemetry, nothing about your code or prompts ever leaves the machine.
It's free to use. A one-time $29 unlocks Premium, no subscription, lifetime 1.x updates. macOS-first today; Windows and Linux folks can grab the waitlist.
I'd love your honest feedback, especially from people who live in Claude Code. What would make this a daily driver for you?
A live HUD for Claude Code makes sense as agents become more like coworkers than autocomplete. Seeing prompts, tool calls, skills, and tokens in one place would help debugging. Are you thinking about session replay or summaries after a run?
I basically live in Claude Code and Cursor, so a native Mac cockpit is exactly the thing I've been missing. Losing track of what's happening across terminal tabs is the real pain. Does it handle multiple parallel Claude Code sessions or worktrees in one view? Congrats on shipping.
The local-only angle is important here; for a Claude Code HUD, I’d care less about another dashboard and more about making pauses, tool failures, and context pressure obvious at a glance.
@randydigital I understand the problem, but I keep wondering how many developers actually care about the mechanics versus the result.
If Claude spends 20 tool calls and 50k tokens but still produces the correct outcome, does the average developer want to inspect the journey? Or is this aimed more at engineering managers and power users who need visibility into cost and behavior?
Feels like there are potentially two very different customers hiding behind the same product.
@randydigital Interesting idea. One thing I’ve noticed with Claude Code is that the more information you expose, the more cognitive load you can accidentally create. At what point does the HUD become another dashboard people monitor instead of something that helps them stay focused?
I’m also curious whether users actually change their behavior after seeing token usage, tool calls, and context consumption in real time, or if it’s mostly reassurance that the agent is doing what they expect. Have you seen any surprising patterns there?
The context-window gauge is the feature I didn't know I needed. I run long Claude Code sessions and the moment it starts compacting is exactly when things get fuzzy - having that fill level in sight beats finding out the hard way. The three-side-tools-into-one-cockpit framing is the right call too; I was squinting at a statusline for the same info. And keeping it all local (reads Claude Code's own data, nothing leaves the machine) is the detail that makes it actually usable for client work. How live is the timeline - true streaming as tools fire, or polled?
I live in the Claude Code terminal all day and honestly the bare CLI experience is fine until you're juggling more than one session — then it's just tabs everywhere and losing track of what's running where. A proper native Mac UI for this seems overdue. Does it let you switch between multiple active sessions easily, or is it more of a single-session viewer?
the interesting fork for a claude code cockpit is where you tap state — parsing the .claude jsonl logs vs wrapping the process for live events. the log route is robust but always a step behind.
Cool tool, the most pain point for me is skill usage, I don't know which skill claude code actual choose in conversation unless I specify to model.
Congrats on putting this together.
The problem is real IMO, especially when managing multiple concurrent agents. But to extend your analogy: if a cockpit has too many flashing lights and live streams, the pilot still gets overwhelmed.
For me, the ultimate HUD wouldn't just stream the raw data—it would summarize it. I’d love a feature inspired by how Gemini handles meetings: if I'm deeply focused on another task for 5 minutes and glance back, give me a quick "catch up" summary of what the agent actually achieved over those 5 minutes.
Distilling the chaos into a quick TL;DR status report.
About Conan on Product Hunt
“A native Mac cockpit for Claude Code”
Conan launched on Product Hunt on June 14th, 2026 and earned 133 upvotes and 20 comments, placing #7 on the daily leaderboard. Conan is a native macOS app that wraps Claude Code in a live HUD — every prompt, tool call, skill, and token, surfaced as it happens.
Conan was featured in Mac (103.6k followers), Developer Tools (515.5k followers) and Artificial Intelligence (473.1k followers) on Product Hunt. Together, these topics include over 189.3k products, making this a competitive space to launch in.
Who hunted Conan?
Conan was hunted by Randy Daniel. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Conan stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Hey Product Hunt 👋 I'm Randy.
I use Claude Code all day, and I kept losing track of what it was actually doing. It'd go heads-down for two minutes firing tools and burning context, and the terminal showed me everything except what I cared about. Which tools did it just run? How full is the context window?
I ended up with a usage CLI in one tab, a cost tool in another, and a statusline I had to squint at. I didn't want three side-tools. I wanted one surface to glance at. A cockpit.
So I built Conan, a native macOS app that sits beside Claude Code and turns its live session into a HUD:
- a streaming timeline of every prompt, tool call, and skill as it fires
- a context-window gauge you watch fill
- a usage and cost pulse
It reads Claude Code's local data. No telemetry, nothing about your code or prompts ever leaves the machine.
It's free to use. A one-time $29 unlocks Premium, no subscription, lifetime 1.x updates. macOS-first today; Windows and Linux folks can grab the waitlist.
I'd love your honest feedback, especially from people who live in Claude Code. What would make this a daily driver for you?
Try it → https://www.conan.sh