Clueprint is live. A Mac app for keeping track of what coding agents leave running.
I've been building Clueprint, a small Mac app that puts your dev servers, Docker stacks and Git worktrees in one place.
Each running environment is grouped under its project and branch. You can see what it's using, open its local port, and review what can be stopped or cleaned up.
I've also been working on how it handles projects that look abandoned. You can tell it you're keeping one, dismiss the suggestion and restore it later. The suggestion stays dismissed until you restore it.
Removing worktrees has a separate set of checks, including uncommitted changes and unpushed commits. Archiving a project moves its files to an _archived folder. You review the action before it runs.
It's out today for Apple Silicon Macs on macOS 14+. Native SwiftUI, with a 14-day trial and no account needed. Pricing is €19 with a year of updates or €39 for lifetime updates.
I'm interested in how this holds up with other people's project layouts. The app needs to make sense of those, not just the ones I happen to have on my Mac.
Interesting approach. What was the hardest part to get right?
Solid lesson. Which channel has worked best for you so far?
Waitlist mostly. Hyping things up and letting people in on launch day.
How did you decide this was worth building in the first place?
That's a good question - I actually had a lot of issues with my M3 Mac Max that went to power on the fans every so often. So I looked into how to optimise this - I'm working with agents daily and I knew which processes consumed the most but they shouldn't have turned on the fans and clog my mac. At one point it even shut off on its own.
So I looked into all the stuff that was running via docker ps and turns out my worktrees never got cleaned up, and I did that manually or with the help of AI from time to time and it consumed a lot of time.
Basically out of necessity. I thought what if cleanMyMac would do more - check worktrees, AI leftover files, etc. And that's how clueprint came to be.
Interesting approach. What was the hardest part to get right?
Interesting approach. What was the hardest part to get right?
Interesting. How are you measuring whether it is working?
Helpful post. How did you get your first bit of traction?
Great breakdown. What feedback have you had from early users?
Interesting approach. What was the hardest part to get right?
Good write-up. What would you do differently if you started again?
Makes sense. Are you planning to charge for it, or keep it free for now?
It's 19 euros for one year worth of upgrades and 39 for a lifetime license.
How did you decide this was worth building in the first place?
The worktree cleanup with the uncommitted/unpushed checks is the part I'd trust most — I've lost work exactly once to nuking a "stale" worktree that wasn't, and never wanted to feel that again. One thing I'd love to see: does it catch orphaned background processes that aren't dev servers or Docker? Coding agents on my machine love to leave file watchers, tunnels, and stray node processes holding ports long after the branch is gone. Grouping by project/branch is exactly the mental model I use, so this clicks for me.
This comment was deleted a day ago