Peer Pool

How the peer pool works

Create a pool with New pool in the sidebar. A pool is a named group of machines that share work.
Add machines with Add a machine on the Machines page. You get a one-time code and a command; run it in PowerShell on the machine. It gets its own key and starts working.
Someone submits a plan — a list of tasks with “must finish first” links — using copilot-peer submit plan.json.
Any free machine claims a ready task. Claims are atomic, so two machines never run the same attempt.
Big tasks can split. Copilot may break a task into subtasks; other machines pick those up, then one machine merges the results.
Leases keep work safe. A running machine renews its lease. If it disappears, another machine takes the task over after the lease expires.

The graph stores only coordination metadata: task text, states, leases and result branch names. Code and results stay in Git.

Pools are private. A new pool is visible only to the person who made it and to people they add with Who can see this pool. Administrators, and accounts allowed to see every graph, see all pools.

Viewers can watch pools. Editors can also create pools, add machines and remove machines. The pool's owner or an administrator can delete it. Cancel a plan with copilot-peer cancel <plan>.

A machine key works only for its own pool. Removing a machine, or deleting its pool, cancels its key; the machine stops by itself within a few minutes. Keys also expire after a set number of days.

Overview

Running now

Recent plans

Plans

All tasks

Machines in this pool

Attempts

How the peer pool works

New pool

Add a machine

Delete pool

Sign in

Running now

Recent plans

Plans

All tasks

Machines in this pool

Attempts

How the peer pool works