Skip to main content

Upgrade to or from 0.8.1

Before any upgrade​

  1. Finish or stop active Agent and Work runs.
  2. Create a manual backup and confirm the backup file exists outside the program directory.
  3. Record the current version and installation type.
  4. Keep the previous installer and backup until the upgraded system has been verified.
  5. Never restore only old program files after a newer version has started against your data. Restore a matching program and data snapshot together.

macOS​

On an Apple Silicon Mac, use Clawuno → Check for Updates, or install the signed 0.8.1 DMG over the existing app. The app upgrades its embedded Engine and preserves user data outside the application bundle.

Intel Macs cannot install 0.8.1.

Windows​

Windows 0.8.1 is the first Clawuno Desktop V2 release. Install it only on a computer without an existing Clawuno program installation. This release does not provide a supported in-place upgrade or migration from the 0.8.0 Engine-only package or internal test builds.

Uninstalling Clawuno Desktop preserves %LOCALAPPDATA%\Clawuno and %USERPROFILE%\clawuno by default. Preservation is not the same as a validated migration path; keep a separate backup and do not point a new installation at unverified state.

Linux​

Upgrade a supported Docker installation from the host. The public 0.8.0 to 0.8.1 path is supported:

sudo clawuno upgrade --confirm-stop

For a named instance, add --instance NAME. The manager downloads the candidate first, stops writers, creates a backup and activates the signed 0.8.1 image. If it cannot complete, preserve the recovery journal and follow the printed recovery command.

Verify after upgrade​

Check the version, sign in, open existing Workspaces, inspect representative files, and run one small Agent task. Also confirm model connections, scheduled Works and linked folders still point to the intended resources.

If startup fails after the new version has begun, stop and use the recovery instructions printed by the installer. Do not delete the recovery journal or point the installation at old code while keeping possibly migrated data.