What they did
Franco started TrendVidia alone in February 2026 and had coding agents write most of its code: a Go virtual machine with a JIT, a UI toolkit, a serialization format in ten languages and more. He wrote the architecture and a short contract every agent session loads. Agents may do anything a revert can undo, such as branches, pull requests, filing issues and rerunning CI, and must ask before merging to main, deleting, spending money, touching credentials or publishing. Three tools run it across dozens of repositories without him: a fixer that groups open issues and starts one headless session per group in its own git worktree, a review daemon that reviews each new commit in a fresh session, and a lander that resumes the author session to answer the review and merge. A question only he can answer is posted on the issue with a needs-decision label and the session waits for his reply.
How it went
By his account the agents produced thousands of merged pull requests in nine months. He lists the failures behind each rule: in one October session three pull-request comments claimed things that were not true, a size cost was reported as 22% when it was 1.8% on the real product, and one repository sat on 96 open issues the pipeline never started while looking like an empty backlog. That last one led him to build a workflow engine that declares the pipeline's states as data.
Worth knowing
He does not name the agent products or models. The rules that mattered most for him: read every status back from where it landed rather than trusting the command that sent it, treat his stated opinions as input and not decisions, and make agents fix problems in the same pull request instead of filing issues by default.