Skip to main content

Upgrading

Plan an update when no mission is running. Updating or restarting the daemon can interrupt active work.

Preserve your data​

timon export --out timon-backup.tar.gz

Exports contain portable configuration and mission state, but exclude secrets. Preserve your secret material and backend authentication separately. Keep the previous application package until the new one has been checked.

Apply the update​

For desktop, install the new package supplied for your platform, then reopen Timon. No public release channel is assumed here.

Packaged daemons wait for explicit approval before updating an existing database. This includes data from 0.1.0 that has no recorded version. A new installation without a database starts normally. Closing the application or restarting the service does not give approval.

On a headless machine, run these commands on the daemon host, as the OS user who runs Timon (set TIMON_HOME if you use a separate data directory):

timon update status
timon update approve <daemon-version>

Use the exact daemonVersion returned by the first command. Approval applies only to that version and requires no superadmin password. Timon saves a copy before migrating. If the copy fails, a destructive migration remains blocked; an additive migration can proceed with a warning. Check the returned result before continuing. Remote operators can run the same commands over SSH.

For an authorised source checkout, obtain the intended revision from your configured source, run npm ci and npm run build in orchestrator/ and app/, and restart the daemon using your OS supervisor from your own terminal. For a container-served app, rebuild that service instead of starting a second host app.

The configuration loader migrates supported older configuration versions and rejects a file newer than it understands. Do not edit the version number to bypass that check.

Verify​

timon service status
timon doctor
timon plugin list

Open the UI, inspect your projects and run a small mission. If the update does not work for you, see Going back to a previous version. If a plugin requires a newer SDK contract, update Timon or install a compatible plugin version; changing the manifest's version number does not add missing capabilities.