Solutions
Can two people's agents work the same backlog?
Updated
Yes. Invite someone into a Thread — the place one job's plan, notes and keys live — and their agents claim from the same board as yours, on their own Mac and their own AI subscription. Only the board crosses between you: their terminals, their code and the rest of your work stay where they are.
Two developers each running three agents is six agents and no shared picture. You paste tasks into Slack, they paste results back, and the actual state of the work lives in whoever last spoke. Screen sharing a terminal does not scale past a demo, and giving a colleague your machine is not an option once real credentials are on it.
The unit of sharing is the job, not the account and not the machine. Each person keeps their own Forkbench account, their own agents and their own subscription to whichever model they use; what is shared is the Thread's board, its plan and the notes and keys you granted it. An agent claims a task, which leases it, so two agents from two people do not pick up the same piece of work — and when a pane closes, its claim releases and the task returns to the pool with its progress intact. That is what lets a colleague's agent continue something yours started overnight. Rungs decide what each person may do: a Viewer reads, a Commenter answers a blocked agent's question, a Contributor creates and claims work and runs agents there, and an Owner invites and sets rungs. Being invited never demands a subscription — the invited person works at the rung you gave them whether or not they pay.
How it works
- 1Give the Thread an objective, so its board is one backlog rather than a list of unrelated errands.
- 2Invite the colleague into that one Thread and set their rung. Contributor is the one that lets their agents claim work.
- 3Let them open their own agents on their own Mac. They see the board, the plan and whatever notes you granted.
- 4Watch claims rather than people: a task shows who holds it and what its last progress line said, which is what stops two agents duplicating each other.
- 5Remove someone when the work is done. Their access ends and the Thread's key rotates.
Straight about the guarantee: Creating a shared board and inviting people onto it are the paid side, and the check reads the board owner's plan rather than the sender's — so somebody always pays for a shared board, and everyone they invite works it on whatever plan they have, including none. A free account you invite is not capped on your board.