Your AI coding sessions vanish into thin air. Here's how to build the tool that captures them.
You've done it. Four hours with Cursor, 40 prompts, 200 file changes, and now you need to write a commit message. You type `fix stuff` and push. Three weeks later you're staring at that commit trying to figure out why you moved that entire auth module and you have absolutely nothing. No transcript, no notes, no breadcrumbs.
This is the AI Session Logger & Changelog Generator problem, and it's real enough that an r/programming thread about vibe coding leaving no trace got 838 upvotes and 423 comments. Developers are openly frustrated. The tooling just hasn't caught up.
Git history is a graveyard of `wip`, `fix`, and `update styles`. Everyone knows this. The existing tools (Commitizen, Conventional Commits) try to solve the format problem, but format isn't the issue. Context is. When you're pairing with an AI for hours, the why behind each decision lives in the chat and then evaporates.
The consultants and freelancers I find most interesting here aren't losing context for aesthetic reasons. They're losing it for financial ones. Client billing disputes, handoff documentation, scope creep conversations. A logged session that shows exactly what was built and when has real dollar value. That's the segment worth targeting first.
Seriously. Don't open VS Code yet.
Here's what I'd do this weekend before writing a single line of code:
Keep it brutally small. You need three things:
A passive session recorder that hooks into Continue.dev or Cursor's extension API and captures prompt/response pairs with timestamps. Start with Continue.dev. It's open source, the internals are inspectable, and you won't be fighting Microsoft's deliberately restricted Copilot APIs.
A diff mapper that, on each file save or `git stage`, associates the most recent prompts to the changed lines using `git diff` output. Yes, the prompt-to-diff mapping problem is genuinely hard in a 3-hour session. Time-window matching will get you 70% accuracy, not 100%. That's fine for v1. Ship something that's useful even when imperfect.
A commit message generator that surfaces a pre-written conventional commit message via a VS Code input box override at commit time. One box, at exactly the right moment, with the context already filled in.
That's it. No web dashboard yet. No team features. Just the extension, local SQLite for storage, and an OpenAI or Anthropic API call to generate the message.
TypeScript for the VS Code extension, because that's just what you use. SQLite local storage so sessions stay on the user's machine and you sidestep privacy concerns entirely. Node.js + OpenAI API for the changelog generation step. The API costs are basically nothing. About $0.002 per session at current pricing.
Once you have 20-30 users and some validation, then you build the Next.js + Supabase web dashboard for PR exports and team changelogs. Then Stripe. The order matters. Most indie hackers build the billing page before they have a user.
Five to seven weeks total if you're building solo. Two weeks on extension scaffolding and session capture. Two weeks on diff mapping and commit message generation. One week on export and a simple dashboard. One week to wire up Stripe and polish for beta.
I want to be honest about what makes this hard, because the idea write-up is pretty optimistic in places.
Microsoft owns the distribution channel (VS Code Marketplace), the AI assistant (Copilot), and the git host (GitHub). They already have all the raw data for this feature. They're choosing not to ship it today, but that's not a structural reason they can't. If Copilot Business ships "session insights" tomorrow, you lose the mainstream market. That's a genuine threat, not a hypothetical.
The API access problem is also real. Copilot's internals are deliberately restricted from third-party extensions. Clipboard interception and screen scraping will break on every update and probably violate Marketplace terms. This is why starting with Continue.dev and Cursor is the right call. Both have accessible APIs and communities that would actually want this tool.
And then there's the willingness-to-pay irony. Developers disciplined enough to care about commit hygiene often already write decent commit messages. The chaotic vibe coders with the worst commit history may not pay for anything. This is why freelancers and consultants matter. They have a financial incentive that pure hobbyists don't.
Free tier gets you 50 sessions a month with local storage only. No web dashboard. This is a real free tier, not a crippled trial.
Solo at $19/month gets unlimited sessions, the web dashboard, PR changelog export, and git hook integration. This is probably where 70% of your paying users land.
Team at $59/month for up to 10 devs, shared changelogs, GitHub/GitLab PR auto-attach. This is where you get meaningful revenue with fewer customers.
Longer term, there's an audit tier at $299/month for compliance exports and AI attribution documentation. That's a different sale to a different buyer, but it's the moat. "Prove what was AI-generated vs human-written" is becoming a real legal and IP question for enterprises, and GitHub Copilot won't own that liability. You might be willing to.
At 20 Solo customers you're covering infrastructure. At 8 Team customers you have real signal that this is a business.
The timing window is probably 12-18 months before Cursor or GitHub decides to build this natively. Both have the same timing signal you do. Cursor's entire brand is being the AI-first IDE and a session replay feature is not a hard two-sprint project for their team.
So the move is to validate immediately, ship fast, get 500+ paying users before the incumbents notice, and then build the audit/compliance angle they won't touch because of liability concerns. That's the actual defensible position. Not the extension itself, but the accumulated session history and the institutional knowledge graph that grows the longer a team uses it.
You can't reconstruct six months of session history after the fact. That's the moat. It's time-dependent, which means the best time to start capturing it is now.