A cofounder that shows its work.
Anyone can generate code. The hard part is knowing what it changed, why it changed, what proves it works, and what it cost. Cofounder answers all four before it asks you to merge.
Cofounder picks the model that fits each step instead of forcing every task through one subscription.
Enough to scope an idea and watch the first real run before any card is involved.
Built for the person who has to answer for the code.
Not for a demo, and not for a team that will review nothing. Cofounder assumes someone owns this product and will be asked what changed.
Three things a chat window will not do.
Cofounder is a system with a memory, a plan and a stopping rule, which is what separates shipped work from a good suggestion.
It reads before it writes
Your conventions, your test commands and your review habits are learned from the repository, not guessed from a prompt.
It delegates, then reviews
Planning, implementation and review are separate jobs handled by different specialists, and the reviewer is not the one who wrote the code.
It stops on purpose
A stop condition is agreed before a play runs unattended, so work ends at a decision rather than drifting until someone notices.
Inside a Cofounder run.
What follows is the part most tools hide: how a request becomes a branch you would be comfortable merging.
It learns how your repo really works
Before the first change, Cofounder records how your app runs, how it is tested, and which conventions the codebase actually follows rather than the ones the README claims.
A team, not a single prompt
Work is split across agents with narrow jobs. Each hands back an artefact, and Cofounder stays accountable for the result that reaches you.
Works where you already work
Watch a run live in the desktop app, pick it up later on the web, or ignore both and review the pull request in GitHub like any other contributor. The work does not live in a chat log you cannot search.
What you get, counted.
The figures that describe the product rather than a growth chart.
Reachable through one workspace key.
Cofounder runs and AI Gateway requests draw on the same number.
Enterprise, with terms set alongside you.
The operational ones.
The broader questions are answered on the home page. These are the ones that come up once you are actually considering it.
Does my repository need tests already?+
No, but it helps. Where a check exists, Cofounder makes it pass before calling work ready. Where none exists, it writes the test alongside the change so the next run has something to prove itself against.
How does it learn our conventions?+
From the repository itself: existing patterns, commit history, lint and format configuration, and the commands your project already uses. It writes what it found into a map you can read and correct.
What if I reject the pull request?+
The branch stays for you to inspect or delete, and the rejection becomes context. Cofounder does not reopen the same change, and a repeated rejection stops the play rather than retrying indefinitely.
Can I stop a run that is already going?+
Yes. Stop it from the run itself and work halts at the current step with its receipt intact. Nothing is left half-merged, because merging is a separate decision that was always yours.
Does it work on private repositories?+
Yes. Cofounder works through the GitHub access you grant and can be scoped to individual repositories rather than an entire organisation.
What languages and frameworks does it handle?+
It is not limited to a fixed list. Because it reads your project rather than pattern-matching a template, the practical limit is whether the repository can describe how it builds and how it is checked.
One sentence is enough to begin.
No migration, no rewrite, no new process to adopt first.