Solutions
Run your AI coding agents across multiple Macs
Forkbench brings every machine paired to your account onto one Thread board, so agents on different machines claim from a single backlog and never touch the same task. What actually travels is the scope: a secret added on one machine is usable from another without the value ever being readable on either, sealed under a key Forkbench does not hold. Removing a machine rotates that key, so revocation is real rather than a delisting.
If you have more than one machine, a laptop and a studio machine, say, running agents on each in isolation means two separate piles of work. There's no shared plan, agents on different machines duplicate each other, and you can't see the whole picture from either one.
Give a Thread one objective; its board becomes a live backlog. Agents on your laptop and your studio machine read that same board, claim open tickets, and hand off cleanly, no two ever on the same task. You see the whole board from any machine, or from the web on your phone. Your Vault travels the same way: a new machine is admitted only by comparing a short code with one already enrolled, and removing a machine means what it had stops working. All of that is free, and so is the rest: owning a board you invite colleagues onto, and answering a stuck agent from the web or your phone.
How it works
- 1Pair each machine to your Forkbench account.
- 2Give a Thread one objective; every Thread already carries the board.
- 3Invite your other machines onto the board and the backlog reaches all of them.
- 4Agents on each machine claim tickets from the one board and hand off; check progress from any machine or from the web.
Straight about the guarantee: The download page lists which builds are available, and takes an address for updates on the rest.