Go on.
Try to merge.
Ivan Antsimonau
Principal engineer · agentic engineering
Abu Dhabi, GMT+4 · open to UAE and EU-remote
My agent crews ship on their own, in production at a secure-communications company and in my own product. The gates decide what gets merged.
Led teams of up to 10 people. Now I run agent crews next to them.
Drag any card into MERGED. The guard will tell you what is missing.
- Push after approval: the verdicts bound to the old commit go void.
- Skip QA: no QA receipt for the head, the merge guard refuses.
- Same check red on 3 heads: the driver parks it and re-plans.
Cost per merged PR: not measured yet.
What the crews refuse
Go on.
Overspend.
My own product, founder-built and self-funded. Every plan gets a price before it runs. Over the ceiling, it plans again.
Status: in development.
farmout
One agent hands work to other coding agents, each in its own worktree. Real dashboard, replayed.
farmout run auto --kind review --brief review.mdgithub.com/tp9imka/farmout =>HALL OF FAME
Measure, then fix
One listener that was never removed held 3.0 GB.
Measure, then fix. Then I built the tool for it: flutter-leak-radar on pub.dev =>
Nothing merges here without proof.
I build the crews and the gates.