Spread AI agent work across machines

Move AI agent work between your team's machines

Every developer machine running the worker joins one fleet. PRFactory keeps a ticket on the machine that started it, lets a person pin it to another, and hands it over with its branch pushed. Each machine runs on its own developer's subscription, so spreading tickets spreads the token spend.

The problem

One developer's agent subscription runs out mid-epic while a colleague's machine sits idle. Moving the work by hand means copying branches around and losing track of who is running what.

How PRFactory handles it

A fleet you can see. Every machine by name, with its online state, the CLI agents it has and the ticket it is running.
A ticket stays where it started. The first claim pins the ticket's later phases to that machine, so the worktree and the previous phase's commits are still there.
Pin it where you want it. Choose the machine on the ticket or when you create it. A manual pin holds even if the machine goes offline.
Move with the work preserved. Moving a running ticket pushes its branch first, and the next machine resumes from it instead of starting over.
Unattended when it has to be. A machine offline past the threshold, or an agent parked on its usage limit, produces the same handover, with the reason recorded.
Fair share. One person queueing ten tickets does not occupy the whole fleet while a colleague's first ticket waits.

Move AI agent work between your team's machines

Let the whole team's machines share the work