Manage machines
Workspace settings → Runners lists the machines connected to this workspace, grouped by the agent each acts as, with the folders they hold underneath.
Who sees what
You see the machines of agents you own. A workspace administrator sees every machine in the workspace, and can pause or revoke any of them.
A machine belonging to somebody else's agent is not shown, and acting on it answers as though it does not exist rather than as though you may not touch it.
What the states mean
| State | What it means |
|---|---|
| Taking work | Connected, with a free slot. Work delegated to its agent can land here. |
| At capacity | Every slot is in use. The next run waits for one to free. |
| Out of disk | The machine is turning work down because it is short of disk. |
| Paused | An administrator stopped it being offered new work. What it is already running carries on. |
| Offline | Not currently connected. It comes back on its own once the runner runs again. |
| Never connected | Bound to an agent but has never reported in. Start the runner on it. |
| Revoked | Cut off. Its agent still works everywhere else. |
Each machine also shows its host, platform, runner version, how many slots are in use, and when it was last seen.
Norn re-reads the page every fifteen seconds, so a machine going offline or coming back shows up without a reload.
Pause a machine
Stop taking work stops Norn offering it new runs. Anything already running carries on to the end. Take work again reverses it.
Pausing is the reversible option, and it survives a restart of the runner — a machine somebody paused does not quietly start taking work again when the daemon restarts.
You can also pause from the machine itself:
norn runner pause
norn runner resume
Revoke a machine
Revoke cuts a machine off permanently. Its credential stops working and its live connections drop within one token cycle.
There is no un-revoke. To connect that computer again you go through connecting a machine from the start.
Revoking a machine is not disabling the agent. The agent keeps working on its other machines and over MCP. If you want to stop the agent entirely, disable it under Workspace settings → Agents instead — that stops every one of its machines at once.
Revoking the agent's API token afterwards does not unbind machines that are already connected.
Connect another machine
Connect a machine opens the two commands to run, for whichever agent you pick. See Connect a machine.
Disconnect a folder
Each folder has Disconnect this folder. It is a state rather than a deletion, so runs that already named the folder keep resolving. See Connect a folder.
From the machine
norn runner status
Says whether the runner is running, which agent it is bound to, its slots, what it is holding, and whether the channel and previews are up.