Skip to main content
Version: 0.8.5

Upgrade, backup and recovery

Change procedure​

  1. Announce a maintenance window and stop new Agent/Work activity.
  2. Record version, image/package identity and deployment configuration.
  3. Create and verify a complete backup. Back up linked folders separately.
  4. Download and verify the target version before stopping the current deployment.
  5. Upgrade through the supported platform manager.
  6. Verify sign-in, data, models, files, Agent runs, Scheduler, Office and Browser runtimes.
  7. Retain the previous package and matching backup until you have checked that the restored or upgraded installation works correctly.

Linux Docker​

Before the first upgrade to 0.8.4 or later, all existing 0.8.1–0.8.3 installations must migrate the selected instance and host manager once, retaining data:

curl -fsSL https://releases.clawuno.com/install.sh | bash

For a named or custom-directory installation, pass --instance NAME or --dir PATH after bash -s --; optionally add --version 0.8.5. Unattended migration must add --yes only after explicit authorization to interrupt active work. See installation examples.

After migration, the host manager uses the same verified CDN path worldwide. For the only instance, run sudo clawuno upgrade. With more than one instance, select the intended target explicitly:

sudo clawuno upgrade --instance NAME

To select an exact signed release rather than the latest stable release, add --version TARGET_VERSION; custom directories use --dir PATH. Automation requires --yes as explicit interruption authorization. Verified cached archives and loaded images are reusable; tags alone are not trusted. An already downloaded file can be supplied with --archive PATH and still requires signed metadata verification. The manager prepares the target before interruption, stops writers, snapshots persistent state, and recreates the instance using the verified image. Same-image upgrades do not restart the Engine or change data, even if the host manager changes.

From 0.8.4 there are no new GHCR releases or regional source choices. install-cn.sh is an argument-preserving compatibility alias. Historical signed files, archives and published images remain available for recovery without deletion or rewriting. Docker itself remains a separate prerequisite, not distributed by Clawuno's CDN.

If startup verification fails before the upgrade transaction completes, the manager leaves recovery information and keeps the deployment stopped. A successfully completed upgrade removes that recovery journal. A problem discovered later does not automatically recreate it. Do not start the old image against data that may have been migrated; preserve the current state and arrange a controlled restoration of the matching old image and data snapshot.

Create and verify a host backup​

sudo clawuno backup --confirm-stop
sudo clawuno start
sudo clawuno status

For a named instance, add --instance NAME to each command. The backup command stops the selected instance and deliberately leaves it stopped. start is a required separate step. The Web backup list does not represent these host snapshots.

Recover a failed upgrade​

Use this only when an unfinished upgrade left a recovery journal for the selected instance and the manager instructs you to recover. It is not a general rollback command for a completed upgrade.

sudo clawuno recover --confirm-restore
sudo clawuno status

For a named instance, add --instance NAME to both commands. Use the recovery record from that same instance; do not copy another instance's snapshot or run an old image against migrated state.

macOS and Windows application backups​

For macOS, create a manual archive in System Settings → Health → Backup & Storage or with ~/clawuno/bin/backup.sh --type manual. Quit the App before restoring with ~/clawuno/bin/restore.sh BACKUP_FILE, then reopen it and verify the data.

For Windows Desktop, create a manual archive in System Settings → Health → Backup & Storage. To restore, quit Clawuno completely, set $engine = "$env:LOCALAPPDATA\ClawunoDesktop\current\engine" and $env:CLAWUNO_DIR = "$env:USERPROFILE\clawuno" in PowerShell, then run & "$engine\bin\restore.ps1" BACKUP_FILE. Remove the temporary environment variable, reopen Clawuno, verify the data, and retain the safety snapshot created before replacement.

These application backups do not include MCP services installed from the Tool Store; after a restore they are downloaded again once npm can be reached.

Backup responsibilities​

Docker backups are host-managed and can briefly stop the selected instance. They do not include linked external folders or MCP services installed from the Tool Store, which are downloaded again after a restore once npm can be reached, and they do not undo actions already sent to model providers, SaaS systems or collaboration platforms.

Test restoration on an isolated host. Check that the backup can restore your data before relying on it for recovery.

Platform boundaries​

  • macOS can update through Clawuno → Check for Updates or by installing the signed 0.8.5 DMG over the app. If an update from 0.8.4.1 or earlier stops with Cannot inspect process, follow Troubleshooting.
  • Linux 0.8.1–0.8.3 installations require the one-time install.sh migration before subsequent CDN upgrades through sudo clawuno upgrade.
  • Windows Desktop 0.8.4 and 0.8.4.1 update to 0.8.5 through Check for Updates or the official 0.8.5 Setup. On 0.8.1–0.8.3, Check for Updates first installs 0.8.4; check again after the app restarts. If you use the old 0.8.0 Engine-only installation, contact Clawuno support for migration steps before reusing its data.
  • After the upgrade to 0.8.5, the conversation index is rebuilt once in the background, and in Workspaces, conversations or Work runs without a current owner become visible only to administrators (see history without a current owner). Returning to an earlier version requires restoring its program together with the matching data snapshot.
  • MCP services installed from Forge with an earlier version show Legacy install, no longer supported after the upgrade and do not run until they are uninstalled and the current version is installed and configured again.