CHANGELOG

Small changes. Better testing.

Stay up to date with new features and improvements.

October 17, 2026Dashboard 2.44.16

See live what each station runs

The station page now shows what each station actually runs and updates on its own as the station reports, so you no longer reload to see whether a push landed.

  • Added the install state to each procedure on the station page: running, installing, install failed, or waiting, with the commit it still runs until the new one is installed.
  • Improved live updates on the station page: the activity timeline and procedure cards refresh as soon as the station reports, catch up after a dropped connection, and stay connected through short network or server interruptions.
  • Fixed repeated "Deployment updated" notifications in the operator view and long commit names hiding the pushed commit on small screens.
October 17, 2026CLI 1.11.6Dashboard 2.44.15

See which stations run each deployment

The dashboard used to show a deployment as pushed even when a station never installed it, and a missed update could leave a station on old code without anyone noticing.

  • Added a per-station status on deployments (Running, Installing, Install failed, Waiting for station, Wrong platform) and a "3/5 running" count in the Deployments list, updated live.
  • Improved stations so they check for deployments every 15 minutes, retry network failures within minutes, wait longer before retrying a deployment that fails to install, and reconnect on their own after losing the dashboard link.
  • Fixed production deployments so stations move to a build only once it is ready, never onto a failed build, and never onto a build made for another platform.
  • Fixed a second station process on the same machine fighting the first one over installs.
October 16, 2026Dashboard 2.44.14

Deploy to stations only from Deployments

The old Commits page deployed versions that current stations no longer install, so every station update now goes through Deployments.

  • Removed manual deploys from the Commits page; old links now open Deployments
  • Updated the Deployments banner to explain where station updates now happen
  • Kept stations deployed from the Commits page running their current version
October 16, 2026CLI 1.11.5Docs 2.5.42

See the operator UI URL on every local run

A local tofupilot run now gives you a browser operator UI by default instead of taking over the terminal, so the run log stays readable and prompts are answered where they render best.

  • Updated local runs in a terminal to serve the operator UI and print its URL, with the plain run log in the terminal; pass --tui for the terminal UI.
  • Added a reminder with the URL each time a prompt or unit identification waits for input.
  • Improved runs next to a station or another run: the default UI picks a free port instead of failing, and CI or --json runs still fail fast on unanswered prompts.
October 16, 2026Dashboard 2.44.13

Pick organizations faster when connecting AI

Connecting an AI assistant to TofuPilot is quicker when you belong to many organizations.

  • Added a select-all checkbox and a single switch to allow write access in every selected organization
  • Improved the authorization screen with a shorter layout that stays compact however many organizations you have
  • Updated the screen to show clearly where the assistant returns after you authorize it
October 16, 2026Dashboard 2.44.12

Restore self-hosted dashboard updates

Self-hosted instances could not update past dashboard 2.44.5, because the images of the releases that followed failed to build.

  • Fixed the self-hosted dashboard image, so version 2.44.12 and later are published again.
  • Brought the dashboard changes announced since 2.44.5 to self-hosted instances, including teammate invitation reminders, standard MCP sign-in for AI assistants and waiting for the operator in the middle of a phase.
October 16, 2026Dashboard 2.44.10

Create up to 50 organizations per account

Teams that split work across many sites, customers or product lines no longer hit the organization cap at 10.

  • Increased the limit on new organizations from 10 to 50 on TofuPilot Cloud: you can create one as long as you belong to fewer than 50.
  • Kept self-hosted instances at one organization.
October 16, 2026Release Server 1.4.23Docs 2.5.41

Accept any character in self-hosted .env values

Self-hosted operators can now put any password or secret in their configuration file, including the characters that used to abort an update.

  • Fixed the deploy script failing on a .env value containing a backtick, a dollar sign, a space or a quote
  • Kept the quotes an operator adds around a value when the script rewrites .env on each deployment
  • Added a clear error with the line number when a value is badly quoted, instead of a silently shortened value
  • Documented how to quote special characters on the self-hosting configuration page
October 16, 2026Dashboard 2.44.11Docs 2.5.40Release Server 1.4.22

Verify who connects GitHub, GitLab or Bitbucket

Connecting a Git provider now confirms that the person connecting it really controls that account, so an organization can only link repositories its own admins own.

  • Improved GitHub connections: TofuPilot checks on GitHub that you own the installation, either as the account itself or as an owner of the GitHub organization, and that the connection was started from your own browser.
  • Improved GitLab and Bitbucket connections: each group or project is claimed per server, so organizations on different self-managed servers no longer block each other, and GitLab now requires a Maintainer token as documented.
  • Improved how account emails are sent, so only TofuPilot itself can trigger them.
  • Updated the self-hosted GitHub setup: add the App's client ID and client secret and enable user authorization during installation before connecting GitHub; GitLab tokens below Maintainer need replacing when they next expire.
October 15, 2026Dashboard 2.44.9Docs 2.5.39

Connect AI assistants with standard MCP sign-in

TofuPilot's MCP server now follows the standard MCP authorization flow, so AI assistants and coding tools connect to your test data with the sign-in they already support, without custom setup.

  • Added support for desktop AI apps that register as native applications, so tools like Cursor connect on the first try.
  • Improved connection security: when an app supports it, its token is bound to that app, so a copied token can't be used on its own.
  • Updated the MCP documentation with connecting several organizations, switching between them, and checking which account a connection uses.

Try these features today