Skip to main content

Backup, recovery and uninstall

A complete application backup contains configuration, authentication data, secrets and managed Workspace data. Linked Workspace folders remain external and need their own backup. Browser cookies and actions already sent to model providers or SaaS systems cannot be recovered from an application backup.

macOS​

Back up​

Open System Settings → Health → Backup & Storage, choose Backup Now, and wait for a successful file, timestamp and non-zero size. Copy at least one recent archive to another protected disk.

Terminal equivalents are:

~/clawuno/bin/restore.sh --list
~/clawuno/bin/backup.sh --type manual

Restore​

  1. Quit Clawuno and confirm the App and local Engine have stopped.
  2. Run ~/clawuno/bin/restore.sh --list and identify the exact snapshot.
  3. Run ~/clawuno/bin/restore.sh "/absolute/path/to/manual-YYYY-MM-DD.tar.gz". The script validates the archive and creates a safety snapshot of the current state before replacement.
  4. Reopen Clawuno and verify sign-in, Agents, Workspaces, model connections and a representative file. Keep both archives until verification is complete.

Uninstall​

Use Clawuno → Uninstall Clawuno. Leave also delete data off to remove the App while preserving local state. Turning it on permanently deletes managed state, including the local Browser profile; linked Workspace folders are never followed and deleted.

Windows Desktop​

Back up​

Open System Settings → Health → Backup & Storage, choose Backup Now, and wait for a successful file, timestamp and non-zero size. The backup list on the same page shows the archive name and configured storage location. Copy at least one recent archive to another protected disk.

Restore​

  1. Stop all Work, quit Clawuno from the tray menu, and confirm Clawuno Desktop and its local Engine have stopped.
  2. Open PowerShell as the Windows user who installed Clawuno and run:
$engine = "$env:LOCALAPPDATA\ClawunoDesktop\current\engine"
$env:CLAWUNO_DIR = "$env:USERPROFILE\clawuno"
& "$engine\bin\restore.ps1" --list
& "$engine\bin\restore.ps1" "C:\absolute\path\to\manual-YYYY-MM-DD.zip"
Remove-Item Env:CLAWUNO_DIR
  1. Confirm the interactive warning, reopen Clawuno, and verify the restored data. Retain the safety snapshot created by the restore tool until verification succeeds.

Uninstall​

Use Windows Settings → Apps → Installed apps → Clawuno → Uninstall. The verified 0.8.1 uninstall removes the Desktop program while preserving %LOCALAPPDATA%\Clawuno and %USERPROFILE%\clawuno.

To erase the preserved state permanently, first verify an external backup, uninstall the app, confirm that no Clawuno process is running, and then delete only those two known Clawuno directories. Linked Workspace folders are outside these directories and are not deleted.

Linux Docker​

Linux Docker backup and recovery are host operations. They are not the archives displayed by the Web backup page. With multiple instances, use the CLI inside the intended instance directory or add an explicit --instance NAME.

Back up​

sudo /opt/clawuno-deploy/clawuno backup --confirm-stop
sudo /opt/clawuno-deploy/clawuno start
sudo /opt/clawuno-deploy/clawuno status

Backup deliberately stops the selected instance and leaves it stopped. Always run start afterward. Copy the resulting host snapshot to protected storage and back up linked folders separately.

Recover an interrupted or failed upgrade​

sudo /opt/clawuno-deploy/clawuno recover --confirm-restore
sudo /opt/clawuno-deploy/clawuno status

Recovery restores the old image, configuration and its matching snapshot together. It preserves the newer failed state separately and does not undo changes in linked folders. Do not start an old image manually against migrated data.

Uninstall​

Remove the container while preserving instance state, configuration and backups:

sudo /opt/clawuno-deploy/clawuno uninstall --confirm-stop

To permanently delete one instance, explicitly name it and type DELETE when prompted:

sudo clawuno uninstall --instance NAME --purge

Purge does not delete linked folders, other instances, shared images, TLS/DNS configuration or external backup targets.

Recovery rules for every platform​

  • Restore only a complete archive created by the same supported release family; never copy individual internal JSON files into a running Engine.
  • Stop writers first and keep the current safety snapshot until acceptance is complete.
  • If a command rejects the archive, path or instance identity, stop. Preserve the installation and collect diagnostics instead of forcing files into place.
  • Perform a restore drill on an isolated installation. An archive that has never been restored is not yet evidence of recovery readiness.