Run a solo company on coding agents under a written contract

Benedicto Franco Jr says coding agents wrote most of nine months of TrendVidia code, thousands of merged pull requests, under a one-page contract and an unattended fix, review and land pipeline.

Done withCustom agentinGitHub· Nov 17, 2026

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.

Try it

With Custom agent· 4 parts to fill in

You work on [repository] under this contract. You may do anything a revert can undo: branch, commit, push, open pull requests, file issues with your analysis, rerun failed CI after classifying the failure. Ask me before merging to [main branch], deleting anything, spending money, touching credentials or publishing outside the project. Treat "I think X" from me as input to test and "adopt X" as a decision. Fix problems you find in the same pull request unless the fix needs a decision I have not made. Before you say pushed, green or passed, read the state back from where it landed and quote failures exactly. If you hit a question only I can answer, post it on [the issue], label it [needs-decision] and stop.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related