I've been building two platforms with Claude Code since April: PowrPlay (a cricket strategy planner and a coaching app, sharing one backend) and an invoice payments platform that's still in stealth. This page is the ledger. Every number here comes from the Git history, the GitHub PR and issue lists, and the Claude Code session log. Nothing is estimated.
Why publish it? Because "I use AI coding agents" means nothing without the receipts. If you're deciding whether this way of working is real, look at the shape of the weeks below, not at the totals.
ezpay carried May and June. PowrPlay (the matchedge monorepo and its backend) took over from the week of July 20, and one week in late July landed 136 commits across the two repos.
Sessions I started on claude.ai/code, on the same week axis as the commits above. I moved most of the work to cloud sessions in mid-August. Before that it ran through the local CLI, which this ledger only sees through the co-author trailers in commits.
June belonged entirely to ezpay. PowrPlay went quiet that month and came back in July.
780 of 839 PRs merged. The median PR is open for under twenty minutes, so a PR here is a reviewed unit of work, not a negotiation.
Commits touching each product's tree. I built the strategy planner in April and May. From the July 27 monorepo split onward, nearly every commit is coaching work: web, mobile and the shared core.
I started tracking work as GitHub issues in June for ezpay and in August for PowrPlay. 219 are still open across the three repos. That backlog is honest; it's what agents surface when you ask them to review their own work.
The primary model named in each commit's co-author trailer. 907 of 941 commits carry one. You can see the model generations roll over as they shipped.
Lines in tracked source, docs and config on the default branch. Lockfiles and images excluded. ezpay's services tier is Java; everything else is TypeScript.
Share of each repository's commits landing on each weekday. Weekends carry about a quarter of PowrPlay's commits and a third of ezpay's. That's what a side project built around a day job looks like.
Default branch only. Active days are distinct calendar days with at least one commit.
96 cloud sessions between July 25 and October 7, 2026, read from the session list on my account.
Three things. First, the agent doesn't change how much you ship per hour as much as it changes how many hours you can ship in. The weekday chart is the tell: a third of ezpay's commits landed on a weekend. Second, the backlog grows faster than it shrinks. 533 issues filed, 219 open. The agent is very good at finding work and only as good as I am at saying no. Third, the model mix tells you when I switched, not which model is best. I moved as new generations shipped and didn't look back.
If you want the longer version, the field notes are coming. This page is the evidence they'll point at.
Sources and limits. GitHub: full PR and issue lists from the repository API, commit history from the cloned default branches (matchedge, ezpay, matchedge-backend), as of October 7, 2026. Commits on unmerged branches aren't counted.
Claude Code: the cloud session list on my account (96 sessions) and the co-author trailers Claude Code writes into commits. Local CLI sessions, token usage and spend aren't included.