Self-improving software
An inside the app, requests that point at the exact element, a queue, a flag, a cloud VM that opens the pull request, and a person who says fixed or not quite. What runs today, and where this is going.
Created November 5, 2026 · Updated November 5, 20264 min read3 chaptersBy Chris Johnston
01 · THE LOOP
People use the software. The software gets the note. The next version answers it.
This is not software deciding what it should become. That idea has its own name, recursive self-improvement. Here, people point and people decide. The do the part in between.
THE TRIP. ONE MADE-UP REQUEST, ALL THE WAY AROUND:
Book a call wraps onto two lines. Fix this.
01
The agent
RUNS TODAY
02
The ask
RUNS TODAY
03
The picker
RUNS TODAY
04
The queue
RUNS TODAY
05
The flag
NOT BUILT
06
The machine
RUNS, STARTED BY HAND
07
The verdict
RUNS TODAY
THE APP
Vercel
THE DATA
Neon
THE CODE
GitHub
THE MACHINES
Beam Cloud
THE MODEL
OpenRouter
One request, all the way around the loop
You are in your app. Something is off.
The Book a call button wraps onto two lines. Nobody planned that, and you are the one looking at it.
You say it: fix this.
Anyone on the team can. The inside the app gets your role and nothing more.
the agent runs as the signed-in person, row by row. That is in the spec, not live in our own app yet.
RUNS TODAY
You point at it.
Tap the button, tap what you mean. The request carries the exact element and page, so it does not need a meeting.
the picker and the chat are two doors today. The spec merges them.
RUNS TODAY
It joins the queue.
Every request in one place, with its history. We built it after one note box kept getting overwritten.
RUNS TODAY
Run it now, or let the team look first.
A flag decides how a request leaves the queue. It decides when the work starts, not what goes live.
this part is not built.
NOT BUILT
A machine wakes and does the work.
It answers with a pull request. A person starts it today. It is not ready to take the queue alone.
RUNS, STARTED BY HAND
How one change runsA person merges.
The fix goes in once someone has read it.
RUNS TODAY
Fixed, or not quite.
Only a person says which. The goal is that whoever asked decides. Today it is anyone whose role holds that right, which on our team is usually the person who asked.
RUNS TODAY
Not quite goes back in the queue.
It runs again with your note attached. Fixed goes back to where you started.
Back at the top. One line.
The button you pointed at is fixed, in the app, where you saw it. The next thing you notice starts the next trip.
03 · WATCH IT



