Who makes Talyn

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

Writing code stopped being the slow part. Landing it did not. A change that takes twenty minutes to write spends two days being a pull request — a test fails for a reason nobody has read yet, the base branch moves underneath it, a reviewer asks for one small thing on a Friday afternoon. None of that is hard. All of it needs somebody present.

Talyn is the attempt to hand that stretch to an agent without handing over anything else: it does not write your features, 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:

• GitHub only. No GitLab, no Bitbucket, and no near-term plan for either.
• No teams. Billing is per account, and shared workspaces, SSO and admin controls do not exist yet. If your company needs to approve a tool before you use it, Talyn probably does not clear that bar today.
• Windows installs are unsigned. SmartScreen warns on first install. The build is fine; the certificate has not been bought.
• It is a public beta and the terms say so. The free plan exists so you can find out whether it works for you before anybody asks you for a card.

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.