Station

Last updated on June 16, 2026

A station is the same TofuPilot CLI installed as a system service on a factory-floor machine. It runs deployed procedures with a live operator UI, auto-updates on every push to your production branch, and uploads reports to the dashboard.

Install the station service

Create the station in your dashboard and open its Install command. The dashboard issues a single-use setup token — valid for one hour, scoped to that one station — and hands you a ready-to-paste command.

Run that command on the bench machine. It installs the CLI, redeems the token, pulls the station's deployments, and registers the service so the station comes back on boot:

Terminal
curl -fsSL https://tofupilot.sh/install | sh -s -- --token <setup-token-from-dashboard>

Behind the scenes it runs tofupilot login --token, which exchanges the setup token for long-lived station credentials and registers the CLI as a systemd unit on Linux or a launchd service on macOS. There is no second command to run.

To turn the bench back into a development machine, log in as yourself again — a plain tofupilot login removes the station service:

Terminal
tofupilot login

Run deployed procedures

Operators open and run the procedures deployed to the station, identify the unit under test, and provide inputs through the same operator UI used in development.

Deploy updates

Link your Git repository, then push to deploy updated procedure code to stations without interrupting production.

Develop — Build and test procedures locally with the CLI in development mode.

Push — Commit and push to your production branch.

Deploy — Select the commit and target stations from the dashboard.

Run — Operators execute the updated procedures without downtime.

Reports

Stations upload reports to your workspace automatically, queuing offline and syncing when connectivity returns so dashboards and analytics stay current.

How is this guide?

On this page