Peon post-mortem
01 tl;dr
Peon was a great tool built on a great idea. It worked really well — before AI. Today it no longer pulls its weight, and I don't have the energy left to rebuild it for the AI era. So I'm shutting peon.dev down. For good.
02 what peon was
A virtual colleague for developers. You told it what to do. It did the task on a schedule, opened a merge request, and you reviewed it, merged it, and went back to the work that mattered.
- fix coding standards, remove dead code, update dependencies
- run Rector, add type hints, fix deprecations
- anything that runs in a shell — if it changed code, you got a merge request
It started out as PHPMate, grew into Peon, and was 100% open source all along.
03 timeline
- INFOPHPMate is born. Mission: give developers their time back.
- OKCarvago hands Rector over to the bot. ~30 min saved per developer, every day.
- OKRenamed to Peon. Recipes, custom tasks, open source.
- WARNAI coding assistants arrive. The bar for "automation" moves overnight.
- WARNAgents now open their own merge requests. Peon's unique edge gets thin.
- FATALMaintainer energy budget exhausted. Graceful shutdown started.
04 what went well
- The idea was right: boring, repeatable work belongs to a machine, not a person.
- The workflow matched how teams already work: task → merge request → review → merge.
- It saved real hours for real teams, and made developers a bit happier.
05 root cause
No single bug. The world just changed. Peon was built for a time when automation meant deterministic scripts on a schedule. Now an AI agent can read a codebase, reason about it, and fix things no script ever could. Next to that, Peon lacks the utility to be worth running.
Bringing it into the AI era would not be a patch. It would be a rewrite. With other, bigger projects to run, I can't give it the energy it would need. Better to end it honestly than to let it rot quietly.
contributing factors: AI ate the use case · finite energy · bigger projects
06 action items
rewrite peon for the AI era— won't fix- shut down peon.dev done
- keep the source code public on github.com/peon-dev done
- say thank you done ↓
07 thank you
To everyone who used Peon, filed an issue, sent feedback, merged one of its merge requests, or just believed in the idea — thank you.
It was a good run, and I'm proud of what it did. ♥
// if you want to get in touch, reach me at
j.mikes@me.com
— Jan Mikeš