Make a PC the machine
Current machine
Serving
One computer serves the project
Inactive computer · ⋯
Make it the machine
Choose the computer that should run the work
Next check-in
New computer serves
The previous machine goes inactive
A project has one machine at a time — the computer whose CLI logins do the work. The first computer to poll when there is no holder becomes the machine. Starting Flowviant on another computer leaves that computer inactive, even when the current machine is offline. It keeps polling until you choose Make it the machine in the app.
The Machines page
Open Project settings → Machines from a project’s sidebar. It lists every computer that has ever polled for this project: hostname, whether it’s serving or inactive, the daemon version it’s running, and when it was last heard from. A computer that has gone quiet still shows up, marked with when it was last heard from — nothing here disappears on its own.
Switching which computer serves
Press Make it the machine on an inactive computer’s row while it is polling. Before you confirm, the page lists the Working, Stuck and Review cards: published code continues from the last pushed commit when it can be fetched; missing work restarts from its brief on flowviant v0.124.1 or later. The code written on the old computer stays there. Branch publishing is the owner’s manual switch for preserving future commits; adding or swapping a machine never turns it on.
The current machine hands off, finishing any deploy already in flight, and the one you picked starts serving on its next check-in. A live old daemon may withhold the move, but a quiet one does not; the confirmation says to update that old daemon before restarting it on this project. The row’s ⋯ menu has Remove, which asks that computer to stand down and takes it off the project. Its login is unaffected — reconnecting later is flowviant login again in that repository.
From a terminal, flowviant machines lists the same information for every project connected on that computer.
If the current machine stops answering, the alert links to Project settings → Machines and names another computer running the project, or says none is running. A machine coming back before you switch carries on with its existing worktrees. Nothing switches automatically after a wait or at startup.
Removing the holder leaves the project free for the first computer to poll. Disconnect also frees it and rotates its credential; the first computer to connect again and poll serves without a switch.
If two computers seem to be running the daemon at once
Flowviant names both, so you can tell which one to stop. Use Remove on whichever one you don’t want serving, or stop the daemon there directly.
Next
Once a machine is serving, write your first card. For what “serving” and “inactive” mean in more detail, see Serving and inactive.