Auto-update
Last updated on November 20, 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.
Held updates
From CLI 2.1.0 on, a station does not install a release its dashboard cannot talk to. When a new CLI needs a newer live link than the TofuPilot server offers, the station keeps its current version, keeps its live view, and logs the reason once:
Update to v2.2.0 held: it speaks realtime protocol 3, this station's dashboard speaks up to 2. Upgrade the TofuPilot server first; the station updates itself after that. `tofupilot update` installs it anyway.The hold lifts on its own once the server is upgraded. It never applies when:
- The server sets a minimum CLI version above the station's: the station updates.
- You run
tofupilot updateby hand: it installs anyway. - The live link is already refused: holding would keep nothing working.
Cloud stations are never held, since the cloud dashboard is always current. On self-hosted servers, CLIs up to 2.0 have no hold: upgrade the server to 2.45.0 before they update to 2.1.0, or set TOFUPILOT_NO_UPDATE=1 on those stations until then.
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.
System packages
Let the deployment venvs of a TofuPilot station import Python packages installed on the machine outside pip, for native dependencies pip cannot install.