Upgrade Clawuno
Release versions (from 0.8.4)
Three-part versions such as 0.8.4 are feature releases. Four-part versions such as 0.8.4.1 fix that feature release and use the same Help Center. A stable release is newer than an internal build with the same base version. Installer package numbers may differ; use the product version shown in Clawuno. Older Windows apps may first offer 0.8.4; check again after installing it to reach later releases.
Before any upgrade
- Finish or stop active Agent and Work runs.
- Create a manual backup and confirm the backup file exists outside the program directory.
- Record the current version and installation type.
- Keep the previous installer and backup until the upgraded system has been verified.
- 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.5 DMG over the existing app. The app upgrades its embedded Engine and preserves user data outside the application bundle. If an update from 0.8.4.1 or earlier stops with Cannot inspect process, follow Troubleshooting.
Intel Macs cannot install 0.8.5.
Windows
Windows Desktop 0.8.4 and 0.8.4.1 can be upgraded to 0.8.5 through Check for Updates or the official signed 0.8.5 Setup. On Windows Desktop 0.8.1–0.8.3, Check for Updates first installs 0.8.4; after the app restarts, check again to reach 0.8.5. Back up first and quit the app before running Setup. If you use the old 0.8.0 Engine-only installation, contact Clawuno support for migration steps before reusing its data.
Uninstalling Clawuno Desktop preserves %LOCALAPPDATA%\Clawuno and %USERPROFILE%\clawuno by default. Keep a separate backup before reinstalling. For a different installation type, confirm the migration steps with Clawuno support before reusing existing data.
Linux
From 0.8.4, Clawuno uses its release CDN worldwide, with no regional source selection or new GHCR releases. Every existing 0.8.1–0.8.3 installation must first run the official installer once to migrate the selected instance and its host manager while retaining data:
curl -fsSL https://releases.clawuno.com/install.sh | bash
Select a named instance with --instance NAME or a custom deployment with --dir PATH. To pin the migration target, pass options after bash -s --, for example bash -s -- --version 0.8.5 --instance NAME. For unattended migration, append --yes only after explicitly authorizing interruption of active work. See installation for complete examples.
After this migration, subsequent upgrades use:
sudo clawuno upgrade
Optionally add --version VERSION and --instance NAME or --dir PATH. Automated upgrades require --yes to authorize interruption. The manager prepares and verifies the target before stopping writers, backing up data and activating it. If it cannot complete, preserve the recovery journal and follow the printed recovery command.
Verified cached archives and loaded images are reusable; a tag alone is not proof of identity. Use --archive PATH for an already downloaded archive, still subject to signed metadata verification. A same-image upgrade does not restart the Engine or change its data, even when updating the manager. install-cn.sh remains a compatibility alias with the same arguments. Historical signed files, archives and published images remain for matched-image/data recovery. Docker itself remains a separate prerequisite, not a CDN-provided dependency.
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.
After an upgrade to 0.8.5, Clawuno rebuilds its conversation index once in the background. Until it finishes, running and unread indicators in the sidebar may be missing and statistics show as preparing; an opened Workspace still lists its conversations. In Workspaces, conversations and Work runs that no longer belong to any current account are then visible only to administrators; see roles and access. If you have to return to an earlier version after 0.8.5 has started, restore that version's program and matching data backup together; otherwise it may not show conversations created by 0.8.5.
MCP services installed from Forge with an earlier version show Legacy install, no longer supported after the upgrade and do not run. Uninstall them in Forge › Tools › Tool Store, install the current version and set up their configurations and Agent or Uno choices again; see Skills and tools.
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.