Auto-update
Last updated on May 21, 2026
When Auto-update is on, the CLI installs new releases at launch and between tests. Stations stay on the latest version without anyone running tofupilot update by hand.
Toggle the setting
Open Stations → Station name → Setup and flip Auto-update. The dashboard pushes the new value to the bench over the live channel, and the CLI applies it on receipt.
When the CLI updates
The CLI checks for a newer release in two windows so the upgrade never interrupts a run:
- At launch. The first thing the daemon does on boot is check for a newer release. If one is available, it downloads and swaps the binary before starting the operator UI.
- Between tests. When the bench finishes a run and is idle, the CLI checks again. If a release is waiting, it installs and restarts in place.
The CLI never updates mid-run. A long-running procedure holds the previous binary until it completes.
Manual updates
Flipping Auto-update off leaves the CLI on its current version. Update manually with tofupilot update or pin to a specific version through your deployment pipeline.
Rolling back
If an update breaks the bench, tofupilot rollback restores the previous version without losing credentials or queued runs.
How is this guide?
Desktop shortcut
Place a TofuPilot shortcut on the station desktop so operators can launch a test run with a single click, with no terminal commands or browser bookmarks.
Offline Upload Queue
Learn how the TofuPilot CLI buffers runs locally when the dashboard is unreachable so no run is lost to a transient outage on the factory floor.