Small changes. Better testing.

When a run failed right at start, the dashboard showed its phases arriving one by one for several seconds and a run time far longer than the station's, while the kiosk showed the error at once.

• Improved live delivery: a burst of phase results now reaches the dashboard in one update instead of one at a time, cutting a ~5 s catch-up to a single round trip.
• Fixed the run and phase durations on the dashboard to use the station's own clock, so they match what the kiosk shows.

The Run and Unit panels of the operator UI now read like the top bar menus, so field names no longer wrap and values line up.

• Updated panel rows to show the field name and its value on one line, with the value aligned right.
• Fixed long field names wrapping onto two lines, such as Serial Number.

The station and the dashboard now share one live view of every run, so a supervisor can follow, help and answer from anywhere while the operator works at the bench.

• Added shared operator forms: a value typed at the station, in the terminal or on the dashboard shows up live on every other screen, and nothing is submitted until someone presses Submit
• Added presence on operator screens: who is here (avatar, name and role), their cursor, the field they are on and who is typing, with viewers watching but never editing
• Improved the live view: a dashboard opened halfway through a long run shows it from the start, and a dropped connection catches up on its own without missing a step
• Improved station commands: every Run, Stop, Pull and answer from the dashboard is confirmed by the station, records who sent it, and never lands on a later run by mistake
• Updated security: only the station itself can publish its run, and live access ends as soon as someone's role or team changes

Stations need CLI 2.1.0 for the live view; older stations keep running and uploading until they update.

A few minor improvements to the operator UI after its redesign, so operators see the state of the station and its procedure at a glance.

• Added the next run pick to the procedure card, with the deployment of each procedure (ID, commit message, when it was pulled).
• Improved the station card: mode, name, organization and how the station starts, the CLI version and status, and the dashboard connection next to the upload queue.
• Updated the procedure list and form controls to match the operator form, and turned sound off by default.

The operator UI is rebuilt so operators move faster at the bench and engineers see everything about a run without leaving the station.

• Added three details levels from the bottom bar: off, a side column of compact panels, or one full tab for the run, plugs, phases, logs or attachments, with search, filters and keyboard shortcuts.
• Improved forms for scanners and keyboards: field-sized controls, short errors, stray scans never answer a question, and every choice has a key.
• Added station and procedure cards in the top bar, a status chip and phase cards in the bottom bar, and recorded sound cues on verdicts and prompts.
• Added the procedure version and description, run metadata and the operator to the run details, and file and line to plug log lines.
• Improved consistency with the dashboard: phase, measurement and log tables now render the same way in both.

Every message the CLI prints now says what failed, names the file, ID or URL involved, and gives the next step on a hint: line, so a failed command tells you how to fix it.

• Improved errors across every command: server errors show the server's message instead of raw responses, procedure.yaml errors point to the line and column with "did you mean" suggestions, and the installers name the URL that failed.
• Added -v, -q and --color flags, with NO_COLOR support, and moved diagnostics behind -v for quieter output.
• Updated output for scripts and agents: --json goes after the subcommand on the commands that return data, every error is one JSON object, and exit codes now mean something (2 usage error, 4 not found, 6 not logged in). Scripts that relied on the old exit code 1 or on message text need updating.

Every station update now goes through the Deployments page, and the API reference describes station access accurately.

• Removed the old Commits page deploy flow: stations now show the version you pushed from Deployments
• Fixed the API reference saying stations cannot use endpoints they can use for their linked procedures
• Updated the station docs to explain how a Git push reaches your stations, with or without auto-push

Studio desktop gets its final update: it is now an offline procedure editor, and stations run on the TofuPilot CLI.

• Removed Station mode from the desktop app: it now shows how to install the TofuPilot CLI on each test station
• Removed every connection from Studio desktop to TofuPilot and Git: it opens, edits and runs procedures locally only
• Added a migration guide in the app: deploy from Git, install the CLI on stations, and write procedures with Studio in the browser

The OpenHTF integration page listed metadata keys and prompt behavior that did not match what the CLI does.

• Fixed the metadata table: the CLI reads serial_number and revision_number, not procedure_id or revision.
• Documented which serial number a run gets under tofupilot run, and that a timed-out prompt returns an empty string.
• Corrected the minimum Python version in the SDK overview and renamed the "Streaming" links to "Remote UI".

The operator UI that streamed OpenHTF tests from the Python client to a dashboard page has been replaced by the CLI, which runs the same unmodified scripts with a live operator UI on any browser.

• Removed the legacy streaming page and the server endpoint older Python clients called to reach it; those clients now stop retrying at once instead of logging a warning every second.
• Removed the "streaming was removed" warning the Python client logged when a script passed stream=True; the argument is still accepted and ignored.
• Planned: the TofuPilot OpenHTF context manager, deprecated with a warning since August 11, 2026, will be removed in a future release. Run your tests with tofupilot run instead, or register the upload() callback if you manage your own pipeline.