Talyn
Merge more. Babysit less.
126 followers
Merge more. Babysit less.
126 followers
Talyn is an AI teammate that watches your GitHub PRs and handles the annoying bits that slow them down. It can fix failing CI, resolve merge conflicts, respond to review comments, and keep PRs moving without you context-switching. Unlike coding assistants that wait for prompts, Talyn works in the background on real PR workflow problems
This is the 3rd launch from Talyn. View more
Talyn
Launching today
Talyn runs Claude Code and Codex in parallel cloud sandboxes, on the plan you already pay for. Close the laptop and come back to a diff, or to a pull request that is already green. Free with 10 box-hours a month. For GitHub, on macOS, Windows, Linux, or the browser.
Free Options
Launch Team
CloudflareYour next app belongs on Cloudflare Workers. Deploy for free
Promoted
Hey everyone, Tom here. I made Talyn.
These days Claude writes most of my code, and my job had turned into babysitting it. Several Claude windows open, laptop lid up all day, and the minute I walked away a PR would fail CI and sit there red until I got back.
So Talyn moves all of that to the cloud. Every task gets its own sandbox with its own branch, agent and terminal. You can start a bunch of them, shut the laptop, and come back to diffs. (A mobile app is coming soon too.)
It runs Claude Code and Codex on your own Claude or ChatGPT plan. I didn't want to pay for tokens twice, so Talyn only charges for the machines.
The part I use most is what happens after the PR opens. Talyn fixes failing checks, conflicts and review comments, and if you queue the PR, it merges once it's green. It won't merge anything you didn't ask it to.
I also didn't want an agent holding my keys. Tokens stay outside the sandbox and get added on the way out, so there's nothing in there to leak.
A few things you should know: it's GitHub only for now and it's a beta built by one person, so expect rough edges, and please tell me when you hit one. Curious what you'd hand off to an agent first!
@tom_owers "close the laptop and come back to a green PR" is the line that got me. I build my whole SaaS with Claude Code. how do you handle secrets in the sandbox, like a DB URL the tests need?
@raghav_21 All the secrets are handled outside of the sandbox, and we use a proxy to then append secrets/variables where it matters.
tokens staying outside the sandbox and only added on the way out is the detail that makes me ok leaving it running overnigth
when it fixes a failing check on its own, do i see the diff before it pushes??? or does it just push and let the next CI run decide???
@thamibenjelloun Hey, with auto fix enabled, it'll push and let the next CI run. This is an opt-in feature though, and so with it disabled it won't fix it push any changes for you.
does it ever run out of github api budget? all of it rides on my user token now if i read the architecture doc right
@bbueno Nope - we track the token budget and make sure to never go over. We also use github webhooks to recieve as much data as possible so we're not polling
where do i see it when claude stops to ask a question?
@leoheo Claude will ask a question in-line - but, if you're using a Thread, then the orchestrator will take care of these questions for you
congrats!! what does it do when two of the parallel ones touch the same file, who wins
@igorblink It uses git to manage all the merge conflicts - so usual merging will apply here!
Hey Tom, congrats on the launch. Talyn looks really interesting. You're right, I'm spending most of my time babysitting Claude Code, and I think this would be an area that would be nice to automate. Looking forward to checking it out.
The babysitting part is exactly where my day goes too. One question before I try it: when you spin up parallel sandboxes, do they share any repo context, or does each agent re-read the whole repo from scratch? That re-read cost is what usually kills parallel setups for me. Also curious whether a sandbox can run an Xcode build and simulator tests, or if it's Linux-only for now.