The Making of Phix

Piece, 2026. A making-of, about a working agent. Directed by Charlotte Joanne; built and written by Claude.

How Phix, an agent that fixes websites, was built in a day, and why it can do the work but can never decide what goes live.

About the Piece

Works For Me imagined a website that fixes itself when a stranger reports a problem, and left one part as a plan: the agent that runs the loop on its own. This is the making of that agent. Everything in it is real, and it happened on 10 November 2026.

Phix is said "fix". It is the agent that reads what people send from the link at the foot of every page Unremarkable builds: "Fix something on this page".

On 10 November 2026, at 07:53, Phix picked up its first real report. It read the page, decided the report wasn't asking for a fix but for different wording, and handed it to me, because the words on my site are mine to change.

That last part is the point of this post. Phix is allowed to do a lot of work. It isn't allowed to decide what goes live, and it was built so that it can't.

Where it started

The fix link already worked. You followed it, said what went wrong, and your report went into a small database. We asked for no name and no email, which meant we could never tell you what happened next.

So I decided three things before anything was built:

Then some smaller decisions, each of which mattered: Phix wakes at 6 in the morning and at midday, UK time. If there's nothing to do, it goes back to sleep without spending anything. Its name is spelled to be found and said to be understood, so wherever it first appears, the page says "said fix".

What happens when you send a report

  1. You send the form. Your report is saved with a key of 128 random bits, and the thank-you page gives you your link, something like unremarkable.me/fix/r/ followed by 22 letters, numbers and dashes.
  2. Your link opens your report's own page. It shows what you sent and "What has happened": a short, dated list, written for you. "Phix has started work on your report." "We found the sentence…" Nothing private ever goes on it, and search engines are told to leave it alone.
  3. At 06:00 or midday, the website checks its database: is there any work? That check is plain code, not AI, so a quiet day costs nothing. If there is work, it starts Phix.
  4. Phix claims the report. Its instructions are to reproduce the problem the way you met it (by screen reader, braille, magnifier, keyboard or agent, if you told us), fix the cause and nothing else, add a test so it can't come back, and put the fixed site on a preview address.
  5. I get an email with a link that works once and lasts a week. It opens a page with your report, what Phix understood, what it changed, the preview, and two buttons: Publish and Reject.
  6. Publish merges the change, and the site rebuilds itself within a couple of minutes. Reject asks for my reasons first, then either sends Phix back to try again or leaves the page as it is, and you see my reasons.
  7. Your page then asks: "Does it work for you now?" You can say it works, or that it still doesn't, which sends it round again. If you don't answer, the report closes itself after 30 days.

If Phix can't fix something, or decides it isn't a fix at all, it says so and the report comes to me. After three tries without a fix I accept, it comes to me anyway.

What Phix is, technically

Phix is Claude Code, Anthropic's coding agent, run by GitHub Actions on my own Claude subscription. Its instructions are a single page in the repository. The website starts it with one call to GitHub. Each run starts from nothing on a fresh machine and is gone when it finishes.

The website is a Cloudflare Worker with a small database. The reports, the private links, the steps and my one-use links all live there.

What Phix cannot do

This is the part I care about most, because Phix reads text written by strangers.

It found problems in the real world

Everything was tested on a copy of the site first: every path, every state of the reporter's page, both buttons, the reminders. The database changes were tried on a copy of the live database before they touched the real one. A test email went out through Cloudflare and arrived.

Then the real thing found what the copy couldn't.

Phix's two runs used about 12 and 21 cents' worth of my subscription.

What I actually did

I didn't write the code. I did:

The agent did the engineering, tested it against the real thing, and stopped at every decision that was mine. Now there's an agent that works the same way after the site is built.

Not on every site yet. Phix can fix unremarkable.me today. Some sites Unremarkable built don't have preview addresses switched on, so Phix sends their reports straight to me, and one is still changed without pull requests, so Phix doesn't have access to it at all.

Read it

If you find something wrong on one of my pages, use the link at the foot of it. Phix will be along at 6 or midday.

Behind the fiction

More about this

More from Blind Ant

About the author

Blind Ant is written and run by Charlotte Joanne. About Blind Ant says more.