Serving and inactive machines
A project has one machine serving it at a time. That’s the computer whose flowviant process is running the daemon, holding the credential, and doing the work for every agent on the board. Any other computer that has connected with the same project credential shows up too, marked inactive.
Open Project settings → Machines to see the list. Each row shows the computer’s hostname, whether it’s serving or inactive, its flowviant version, and when it was last heard from — “heard 12s ago” while it’s actively polling, “last heard 3d ago” once it’s gone quiet. A quiet row isn’t deleted; it stays listed so you can tell a machine you forgot about from one you’re using.
To move a project onto a different computer, press Make it the machine on that computer’s row. This only appears on a row that’s inactive and still polling — a machine that’s stopped isn’t a place you can move to. The switch isn’t instant: the current machine finds out on its next poll and stops serving then, and the app shows this as “Moving” rather than “moved” until that happens.
If the machine currently serving the project is running an old flowviant version and is still being heard, Make it the machine stays withheld until you update or stop it yourself. A quiet old machine no longer blocks a swap. The confirmation says to update it before restarting it on this project.
The confirmation lists the current machine’s Working, Stuck and Review cards. Published branches continue from their last pushed commit if they can be fetched. Missing code stays on the old computer, and flowviant v0.124.1 or later restarts those cards from their briefs; earlier versions leave missing work Stuck. Earlier deliveries stay in the cards’ history. When branch publishing is off, the confirmation says so: only the owner can turn it on to preserve future commits on GitHub. Swapping never turns it on. A deploy already running on the current machine finishes before that daemon hands off.
Starting Flowviant on another computer leaves it inactive. It keeps polling, however long the current machine has been silent. Only Make it the machine moves an existing holder.
If the current machine stops answering for ten minutes, Flowviant alerts the project admins. The alert names another computer running this project that can take over, or says none is running, and links to Project settings → Machines. If the current machine returns before anyone switches, it carries on with its existing worktrees.
A project can also have no holder — before its first connection, after the holder is removed, or after Disconnect. The first computer to poll with the current credential becomes the machine without a switch. After Disconnect, each computer needs to connect again.
See Make a PC the machine for connecting a computer for the first time, and Removing a machine for taking one off the list for good.