Remote UI

Last updated on November 19, 2026

The Operator UI mirrors a running Station into the dashboard. The view renders the same procedure flow, prompts, and measurement readouts the operator sees on the bench, with sub-second latency. Members with the right access answer prompts from the browser, fill forms together with the operator, and see who else is watching.

Open it from Stations → Station name → Operate, or jump straight to /<organization>/operator/<station>. A single-station organization skips the picker and lands on the only bench.

Requirements

ComponentVersion
Station CLI2.1.0 or newer
TofuPilot dashboard2.45.0 or newer (cloud is always current)

A station and a dashboard on different versions keep running tests, uploading runs, and receiving deployments. Only the live view and dashboard commands are off until both sides are current. See Version compatibility.

What the dashboard shows

  • The active procedure, version, and unit under test.
  • Every phase outcome as it lands.
  • Live measurement readouts and limits.
  • Operator prompts waiting for input, with the values being typed into them.
  • Who else is on the station, and where their cursor is.
  • Elapsed time and queue status when the bench is offline.

Open a run that already started

A page opened in the middle of a run shows the run from its start, not only what happens after you arrive. The station keeps a snapshot of the run (its start, the open phases, the open prompts and the values typed into them) and the dashboard joins it with the events published since.

If the page or the station loses its connection for a moment, the dashboard notices the missing events and loads a fresh snapshot, so no phase goes missing. When a station could not keep every event (a very long or very busy run), the view says it shows a partial replay.

Fill prompts together

Every field of an open prompt or identify form has one shared value, held by the station. When someone types on the kiosk, in the terminal UI, or in a dashboard tab, every other screen shows the value as it changes, letter by letter.

BehaviorDetail
Supported fieldsText, number, slider, switch, choice, select, multiselect, checklist.
LatencyAbout 0.2 s between screens.
Two people in the same fieldThe last edit the station receives wins. Every screen ends on the same value.
Reloading a pageThe form comes back with the current shared values.
FocusA remote edit never moves your cursor or your focus.
SubmittingTyping never submits anything. The prompt closes only when someone presses Submit, and the answer is validated as before.

Scan protection and the Enter guards on text fields work as usual.

Answer a prompt

The first answer the station accepts closes the prompt on every screen, with that answer's values.

  • Two answers at once. One wins. The other screen shows "Camille answered first. Your answer was not used."
  • A rejected answer. The form comes back with the error and shows what others typed while the answer was being checked.

Local runs share nothing

Shared values exist only on a station running as a service (tofupilot service start). A standalone tofupilot run on a development machine, and a Studio session, keep each form local to its screen. Answering from either the kiosk or the dashboard works as before.

See who is here

The top bar shows one avatar per person on the station, ringed in their color, at its right end. The same person in two tabs is one face, and everyone at the bench (kiosk and terminal UI) is one face with a monitor icon. Past three faces the rest fold into +N.

Hover a face to see the name and role:

WhoLabel
A dashboard memberCamille Martin · Admin, Camille Martin · Viewer, …
The bench<Station name> · At the station

The picture is the member's uploaded avatar, or the one from their sign-in provider (Google, GitHub). Initials show when there is none. Name, role, and avatar come from the signed session: a browser cannot claim to be someone else.

Inside the form:

  • Cursors. Each person's pointer shows on the other screens, with their name, in their color.
  • Rings. A colored ring with a name marks the control someone is on: text field, slider, switch, select, or any other prompt component.
  • Typing. Text fields show "Camille is typing…" while keys come. It clears three seconds after the last key, and the ring stays while the field has focus.
  • Leaving. A person who closes or hides the tab leaves the stack within a few seconds.

Presence says who is in which field, never what they type: typed values travel only as shared values, under the rules above.

Commands from the dashboard

Members with write access send commands to the bench:

  • Run a procedure.
  • Stop or Kill the current run.
  • Pull now, from a procedure's menu on the station's page, to check the station's deployments at once. It also retries a deployment whose install failed, without waiting for the station's back-off.
  • Change settings in the Station configuration panel.

Each command is recorded with who sent it and when. The station confirms receipt within about a second. If it stays silent for five seconds, the dashboard warns that the station did not confirm the command. When the problem is on your side (your page lost its connection), the warning says so instead of blaming the station.

A Stop or Kill targets the run on screen when you press it. A station that has already finished that run, or moved on to the next one, ignores it. A command older than 45 seconds is dropped, so a command delayed by a network outage never lands on a later run.

How it works

The CLI and the dashboard talk through a realtime server, on four channels per station:

ChannelCarriesWho publishes
RunRun events, prompts, shared values, the online badgeThe station
HealthTelemetry, hardware, deployment and update statusThe station and the TofuPilot server
CommandsRun, Stop, Kill, Pull now, settingsThe TofuPilot server only
PresenceCursors, focus, typing, who is hereEvery participant

The dashboard subscribes through a short-lived token. A browser never publishes a command or a shared value directly. It asks the TofuPilot server, which checks the member's rights, signs the request with the member's identity, and forwards it. The station accepts publications on its own channels only from its own connection.

The station keeps the run's snapshot up to date: when it connects, at the start and end of each run, every 250 events, after two quiet minutes, and before it disconnects.

Identity

CallerChannel scope
Station API keyPublishes on its own station's run and health channels.
User sessionSubscribes through a token signed for the user's organization, valid ten minutes. Cannot read another organization's channels.

The token refreshes transparently on both sides. A member removed from the organization, whose role changes, or who loses access to the station through a team change is disconnected within seconds and reconnects with their new rights, or not at all.

Permissions

RoleOperator UI
Owner, AdminWatch, answer, edit shared values, and send commands on any station.
DeveloperWatch, answer, edit shared values, and send commands on any station.
ViewerWatch stations in their access group scope. Typing in a field changes only the viewer's own screen; nothing is sent.
OperatorDrives the station they sign in to from the bench.

Write access goes only to members whose role and access group scope include the station; everyone else watches read-only. Everyone on the page appears in the avatar stack, viewers included.

Version compatibility

The station and the dashboard agree on the live link version each time the station connects. When they do not match, the station page says which side to update:

NoticeCauseFix
Station CLI needs an updateThe station runs a CLI older than 2.1.0.The station updates itself. To update now, run tofupilot update on the station.
TofuPilot server needs an updateA self-hosted server older than the station's CLI.Upgrade the TofuPilot server.
Live view off: the realtime server needs an updateA self-hosted realtime server with an older configuration.Re-run the TofuPilot deploy script.

During a mismatch, the station runs tests, uploads runs, and pulls deployments every 15 minutes. The live view, dashboard commands, and deployment status come back on their own once both sides are current: the station asks again every 30 minutes, with no restart.

From CLI 2.1.0 on, a station does not auto-update to a release its dashboard cannot talk to.

How is this guide?

On this page