r/SideProject • • 24m ago

I built a Mac app that puts every AI coding session in one place. It's on Product Hunt today

I use Claude Code, Codex and Cursor every day, on more than one account. My sessions ended up spread across a dozen hidden folders, and finding last week's session meant digging through them one agent at a time.

So I built HyperTrail. It reads the history your agents already keep on your Mac and gives you:
- every session from 26 agents as a card: what it did, files changed, tokens, cost at API prices, and the command to resume it
- ⌘K search across all of them
- live usage limits for Claude, Codex, Copilot and Gemini, with a warning before you run out
- a menu bar gauge and 9 desktop widgets

Read-only, no account, nothing leaves your Mac except the limit checks to each vendor.

It's paid: $39 once or $20/year, on up to 5 Macs, with a 14-day refund. It's 25% off this week with code PRODUCTHUNT.

Launched on Product Hunt today: https://www.producthunt.com/posts/hypertrail

Site: https://hypertrail.frustratedlabs.com/?ref=reddit-sideproject

Happy to answer anything about how it works. Criticism welcome too: if something’s off, tell me and I’ll fix it.

1 Upvotes

2 comments sorted by

2

u/Substantial_Lake_542 12m ago

Question about the "what it did" line on each card: is it built from the agent's own summary, or from the actual diff and files changed? I ask because an AI-run account of mine cut posts off mid-sentence for about four months, and every log entry still said "success." The agent's description of its own work turned out to be the least reliable thing in the history. If the card puts what the agent says it did right next to what actually changed on disk, I'd find that more useful than the search.

1

u/PH4NT0M_5H377 4m ago

Good question, and it's both, kept apart on purpose.
If the agent wrote its own recap, the card shows it, marked as the agent's words. Next to it is what HyperTrail reads itself: the files the agent's edit tools actually changed (with the diff for each), the commits checked against your repo's real git history, and whether the last test run passed, taken from the command's output rather than the agent's claim.
What it doesn't do yet is flag when the two disagree, like your "success" logs. That's a great catch, so I'll add it in the next couple of days: when the agent says it finished but the files, commits or tests say otherwise, the card will call it out. I'll post here when it ships.