The Agents page
Where you connect and manage your own host machines.
The Agents page lists the host machines you've connected to Fragua. Each one is a computer of yours running the command-line tool, ready to pick up work. It's where you watch a machine come online, see what it's handling, and forget it when you're done.
A note on the name: here, an "agent" means one of your machines — a connected host — not one of the AI agents that write briefs or build features. The page answers "which of my computers can run work right now?"
Everyone brings their own
Agents are personal. Every user connects their own machine with their own token, so each person runs work on hardware they control. Several teammates can share a workspace and each still runs on their own host. You set a machine up by running fragua login on it — see The command-line tool.
-
One token per person — your token is yours, stored securely on each machine you connect; it isn't shared with the workspace.
-
As many machines as you like — connect a laptop and a desktop and a server — each shows up as its own row.
-
Forget any time — removing a machine here revokes it; it stops picking up work right away.
What each machine shows
Every connected machine reports its state so you always know whether work can run.
Whether the machine is connected right now, and when it was last seen. A machine that stops checking in shows as offline.
How many agents it's running versus the most it will run at once — the concurrency you set when connecting it.
Which workspaces this machine has set up and can run work for. A machine only handles repositories it has cloned.
The operating system and the tool versions it's running, so you can spot a machine that needs an update.
How work finds a machine
When you start a run, Fragua sends it only to your own machines — never to a teammate's. It picks one that's online and set up for that workspace, hands it the work, and the machine streams back what it's doing. A multi-turn conversation or a continued build stays on the same machine that started it.
If none of your machines is online when a run is ready, Fragua tells you so you can connect one — the work waits rather than failing.
From a spec, an issue, or a planning agent in the web app.
One of your online machines, set up for that workspace, claims the work and runs it.
The control plane shows the live log and cost while the work happens on your machine.
A run goes to its owner's machine — yours runs on your hardware, a teammate's on theirs.
The CLI guides walk through connecting one and the full command list.