Who makes Talyn

Talyn is built by one person, in public, on the repository it manages. What that means for you, and what it is not ready for yet.

Talyn is built by Tom Owers. It is not a company with a team behind it, and it would be easy to leave that vague on a page like this. It is one person, working in public, and you can watch the whole thing happen in the repository.

Why it exists

Agents write most of a change now, and the slow part moved. You wait for one agent to finish before you start the next. Your laptop has to stay open while it works. Then the pull request it opens spends two days going red: a test fails, the base branch moves, a reviewer asks for one small thing on a Friday afternoon. None of that is hard. All of it needs somebody present.

Talyn gives every task its own agent in its own cloud sandbox, so you can start as many as you have tasks, close the laptop and come back to a diff. Then it takes the work the rest of the way, to a merged pull request. It runs on the Claude or ChatGPT plan you already pay for. It does not want your API key, and it does not merge anything you have not flagged.

It is built on itself

The merge queue drains Talyn’s own pull requests. The code reviewer reviews its own code. When something on this site says a Standard review takes about half an hour, that is a measurement off a real run, not a target, and it is published in that shape because promising “a few minutes” is how a feature that is working comes to feel broken.

What it is not ready for

Worth knowing before you spend an afternoon on it:

Getting hold of me

Bugs, questions and arguments all go to GitHub issues. Everyone who uses Talyn has a GitHub account, so that is one fewer account than a support portal, and it keeps the answers where other people can find them.

The quickest way to judge it is to give it the task you keep putting off.

Free with 10 box-hours a month, on the Claude or ChatGPT subscription you already pay for.