Docs · Machines
Machines
Every Anvil is a node that can run threads and checks for the others. Add the machines you have and work goes to whichever has room.
Adding one
Install Anvil on the machine (any platform), then add it from one you already use. Anvil reaches it over SSH:
anvil machines add workbox --target you@workbox
A machine reports its platform, cores, memory, load, sessions and which agents are signed in there. Machines you add to your team's forge are shared with the team.
The queue
Threads and checks wait in one queue. Each starts on a machine that's reachable, has what it needs (a platform, an architecture, an agent signed in, the repository) and has room. A waiting item says why it waits.
anvil queue add --project harbor --on auto --after-lane spike \ --prompt-file brief.md
An item can wait for a time, for another thread to finish, or for a branch to land on main.
Budgets
Each machine has a budget: the most agent sessions it runs at once, 80% of its cores to start with. The scheduler never goes past it, and holds work back from a machine under load.
Moving a thread
anvil thread move 9f449e93 --on workbox
Between turns, a thread's work is committed to its branch, its conversation goes with it, and it carries on on the other machine. Everything between machines goes through the machine you're on, so a laptop on one network and a server on another can trade threads.