Two tools I built for myself. Both free.
I write my own tooling because the work needs it, not because I set out to sell it. Two of those tools turned out to be useful enough on their own that they are public, free and MIT licensed. If you write software with AI, they are aimed squarely at you.
No signup, no account, nothing to buy.
MIT licensed · runs on your own machine · nothing is uploaded anywhere
Find out how you actually work with Claude Code
Every Claude Code session you have ever run is already written to disk on your machine. This reads that history and hands back a specific account of how you work, with the evidence attached to every claim. Mine came to 2,105 files and 2.2 GB.
What you explain over and over
The context you retype every session because it was never written down once. That is usually the cheapest thing on the list to fix.
What you keep correcting
The same instruction, given a hundred different ways. What someone corrects repeatedly is much harder to fake than what they say about themselves.
What a session costs before you type
The tokens your setup spends loading itself. Mine was 46,063 before the first word. Most people have never counted theirs.
Commands you have run by hand, repeatedly
One of mine had been typed out 44 times. Anything at that count is a script you have not written yet.
Approve or skip, one at a time
It proposes changes to your setup, and nothing is applied until you say so. You keep the report either way.
It never leaves your machine
The transcripts are read locally and the report is written locally. Nothing is uploaded, and there is no server to upload it to.
Run several Claude Code sessions at once, on Windows
Once you run more than one coding agent at a time, two problems show up immediately. You cannot see what any of them are doing, and sooner or later two of them edit the same file and one quietly loses. On macOS and Linux people reach for tmux. On Windows there is nothing to reach for, so I built this instead.
Real terminals, not hidden processes
Every agent runs in a visible terminal window you can watch, grab and type into yourself, placed on its own virtual desktop.
One dashboard over all of them
Spawn an agent, see the whole tree of who spawned whom, and send a line into any session from the browser without stealing focus from whatever you are doing.
File locking between agents
Before an agent edits a file it has to take a lock. If another agent holds it, the edit is refused and the agent is told who has it, so it goes and does something else instead of overwriting the work.
A rationed message bus
Agents can talk to each other, but only about a named shared thing: a file, a contract, an unresolved decision. Status narration is deliberately not a use case.
Restart without losing the fleet
State is rehydrated on start, so restarting to pick up new code costs nothing and the terminals survive it.
Windows first, on purpose
Keystroke injection and desktop placement are built on Windows APIs directly. That is the whole reason it exists, and it is not portable.
STATUS Being prepared for release. It runs here every day and the test suite is green. What is left is the tidying that turns a personal tool into one a stranger can install.
Because I did not build them to sell
Both of these came out of my own work. I needed to know where my time was going, and I needed several agents to stop overwriting each other. Neither was a product decision. Once they worked, putting them behind a payment would have meant maintaining a business around them, and I would rather maintain the tools.
There is a second reason and it is fairer to say it than to pretend otherwise. If you are deciding whether to hand me your business's software, the most honest thing I can show you is the code I write when nobody is paying me to write it. Read it. It is all there.
If you use either one and it breaks, or it tells you something surprising, I would genuinely like to hear about it.
I build this kind of thing for businesses too.
Most of what I do is not open source. It is custom software, AI automation and the internal machinery a business runs on, built for one business at a time. If that is closer to what you need than a website is, tell me what the work looks like.