# TofuPilot's Operator UI
URL: /operator-ui-tofupilot
Run OpenHTF tests from a hosted operator interface with HTTPS, user accounts, multi-test support and searchable history — no test code changes.
Run the same OpenHTF script, but serve the operator interface from a central, authenticated web app instead of `localhost`.
The bundled OpenHTF Operator UI is a good fit for one bench: it starts with the script, shows prompts and live phases, and needs no infrastructure. Its limits show up when a line has several stations, when engineers want to watch a station from their desk, or when someone asks for last week's runs. TofuPilot's Operator UI covers those cases.
Feature / Limitation
OpenHTF Operator UI
TofuPilot Operator UI
**Test support**
Single test only
Multiple tests, switchable from UI/API
**Test history**
In-session only (or a local `history_path`)
Built-in searchable history across stations
**Hosting**
Localhost
Centralized, secure (HTTPS + auth)
**Access from other machines**
Manual network config required
Accessible via URL, no extra config
**Security**
No HTTPS, no user management
HTTPS + user authentication
**Setup complexity**
Manual setup + script changes
1-line integration
The built-in multi-station dashboard lists stations on the LAN but still serves each station's UI from that station, without authentication or history.
Run your existing test with the TofuPilot CLI — `tofupilot run .` — without modifying your test logic. You can run it in parallel with the OpenHTF UI to compare both outputs live. Operator prompts (`UserInput.prompt`, `prompt_for_test_start`) render the same way, including `image_url`.
Learn more in the TofuPilot Docs