Install Clawuno
macOS
Requirements: Apple Silicon Mac and macOS 13.5 or later.
- Download Clawuno 0.8.4 for macOS.
- In Terminal, run
shasum -a 256 ~/Downloads/Clawuno-0.8.4.dmg. Compare with the DMG SHA-256 in the 0.8.4 Mac release manifest. Check that its version and filename are exactly 0.8.4; do not use another version's checksum. - Open the DMG and move Clawuno to Applications.
- Launch Clawuno from Applications. Do not bypass a macOS warning that the signature is invalid; download the official package again instead.
- Wait for the Engine to start, then complete first-run setup in the app.
The macOS app owns the local Engine lifecycle. Opening the app starts it; quitting the app stops its managed Engine and Scheduler. While the signed-in Mac user keeps Clawuno running, this complete Engine can also serve remote Desktop or browser clients. Use a protected HTTPS/private-network origin and verify remote sign-in with the administrator email and password configured under System Settings → Users → Set up remote login before sharing it.
Windows
Requirements: Windows x64 and an interactive desktop user session.
The 0.8.4 installer uses Azure Artifact Signing Public Trust rather than the 0.8.1 self-signed certificate. SmartScreen reputation and organization policies are separate: a valid signature does not guarantee that no warning appears. Verify the signature and exact file hash; do not disable security controls to bypass a mismatch.
- Download Clawuno 0.8.4 Setup.
- Open PowerShell in the download folder and verify the file:
Get-FileHash .\Clawuno-0.8.4-windows-x64-Setup.exe -Algorithm SHA256
Compare the result with the Windows x64 Setup SHA-256 in the 0.8.4 signed release manifest. Check the exact version and filename. Stop if the manifest is unavailable or the hash differs.
- Run Setup only after checking its signature and matching the file hash to that release manifest. Do not disable security controls to bypass a mismatch.
- Launch Clawuno from the Start menu and wait for the managed Engine to become ready.
- Complete first-run setup in the Desktop app.
Clawuno Desktop and its Engine Host run in the signed-in user's interactive session. While that user keeps Clawuno running, the complete Windows Engine can also serve remote Desktop or browser clients. Use a protected HTTPS/private-network origin and verify remote sign-in with the administrator email and password configured under System Settings → Users → Set up remote login before sharing it. Linux Docker remains the better fit when the Engine must run unattended without a signed-in desktop user.
Linux
Requirements: x86-64 or ARM64 Linux, Docker Engine, Docker Compose v2, Python 3.9 or later, curl and openssl. Reserve at least 12 GiB of free space for installation and extraction. The installer selects the signed image for the host architecture automatically.
Docker itself is a separate prerequisite: Clawuno's CDN distributes Clawuno, not Docker Engine or Compose. Prepare Docker and verify daemon access before deployment.
From 0.8.4, Linux installation and upgrades use the Clawuno release CDN worldwide, without a regional selector or new GHCR releases. New installations and all existing 0.8.1–0.8.3 installations, regardless of their original download source, use the same command:
curl -fsSL https://releases.clawuno.com/install.sh | bash
For existing installations, run this once to migrate the selected instance and update its host manager, retaining its data. Wait for active work to finish; migration can interrupt the selected instance. With multiple instances, add --instance NAME or --dir PATH to select the target. To pin a release, add --version 0.8.4:
curl -fsSL https://releases.clawuno.com/install.sh | bash -s -- --version 0.8.4 --instance NAME
Replace NAME with the intended instance name, or use --dir /absolute/deployment/path instead. For unattended migration, append --yes only after explicitly authorizing interruption of active work:
curl -fsSL https://releases.clawuno.com/install.sh | bash -s -- --instance NAME --yes
After this one-time migration, use the host command for subsequent upgrades:
sudo clawuno upgrade
The upgrade command also accepts --version VERSION and --instance NAME or --dir PATH. Automated upgrades require --yes to authorize interruption. An old manager that requests an installer update must be migrated with install.sh, not repeatedly retried.
Downloads are checked against signed release metadata, including archive size, SHA-256 and image identity. Cached archives and loaded images are reused only after verification; a matching tag alone is not trusted. An already downloaded archive can be supplied with --archive /absolute/path/image.tar.gz to the installer or upgrade command; it still requires matching signed release metadata and is not a verification bypass. Repeating the same-image upgrade does not restart the Engine or alter its data, even if the host manager is updated.
install-cn.sh remains an argument-preserving compatibility alias, not a separate regional choice. Historical signed files, archives and published images remain available for recovery; they are not deleted or rewritten. Recovery must restore the matching image and data snapshot, not simply run older code against newer data.
The installer binds Clawuno to host loopback by default. Do not expose the Engine directly to the public internet; use an authenticated reverse proxy or an SSH tunnel.
After installation:
sudo clawuno list
sudo clawuno status
To display the private administrator setup link again, run sudo clawuno open on the Linux server. If you use an HTTPS reverse proxy, replace only the http://localhost:<port> origin with your HTTPS domain and keep the complete /sign-in#setup_token=... suffix. The link contains the private installation credential required to create the first administrator; do not share it.
Confirm installation
After setup, verify all of the following:
- the displayed version matches the release you installed (
0.8.4); - you can sign in again after a restart;
- a model connection can pass its connection test;
- a Workspace, Agent, Chat and Work can be created;
- a small file can be uploaded and downloaded without changing its contents.
If the Engine does not start, continue with Troubleshooting rather than repeatedly reinstalling over the same data.