Launching today
Conan
A native Mac cockpit for Claude Code
91 followers
A native Mac cockpit for Claude Code
91 followers
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.
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
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.
@rightsum Totally fair, the flashing-lights problem is real. right now Conan leans toward the raw stream (every prompt, tool call, skill, token as it happens) but you're right that past a certain pace you want the distilled version, not the firehose. a "what did the agent actually do in the last 5 min" catch-up summary is a great idea, especially with multiple agents running. putting it on the list. appreciate the thoughtful take.
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.
@qifengzheng We went hooks-first instead of log-tailing. Claude Code's hook system pushes events to a local gateway live, so we dodge the "step behind" problem. Logs are still useful for history backfill, and we scrape the live TUI frame for the stuff that's neither logged nor hooked (/context, /usage token counts).
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.
@sleekzheng this is actually one of the main things Conan tries to solve. the Timeline shows which skill fired on each turn, and since Claude Code doesn't expose its own skill scoring, there's a heuristic that also surfaces which skills were considered, not just the one that won. so you get to see the choice happening instead of guessing. curious if that's the kind of visibility you were after.