Skip to main content

Plan and deploy 0.8.1

Choose the Engine host​

macOS, Windows and Linux can all host a complete Clawuno Engine for remote users. The operating system does not decide whether a machine is a “server”; the important difference is how the Engine lifecycle is managed.

Host formCan serve remote usersLifecycle and best fit
macOS app on Apple SiliconYesThe app manages the Local Engine. The Mac user must remain signed in and Clawuno must keep running. Suitable for a managed workstation or a small shared deployment.
Windows x64 Desktop appYesDesktop and EngineHost run in the signed-in user's session. Suitable for a managed workstation or a small shared deployment.
Linux x64 DockerYesDocker manages an Engine-only deployment without a desktop session. Best for an unattended, continuously available or centrally operated server.

The macOS and Windows packages include the same complete Engine and Web Client used by remote users; they are not client-only applications. Linux Docker is the preferred always-on form, but it is not the only platform that can act as a server.

Prepare a macOS or Windows host​

  1. Install the official 0.8.1 app by following the platform installation guide, open it and complete first-run setup.
  2. Keep the host user signed in and keep Clawuno running. Explicitly quitting the app stops the Local Engine it manages and interrupts work on that Engine.
  3. During the required 0.8.1 first-run setup, create the administrator with a name, real email address and password. Verify those same credentials from the intended protected remote origin before inviting users.
  4. Give the Engine a stable, protected origin as described under Network boundary. Record who owns the host session, app updates, backups and restart recovery.

Prepare a Linux host​

  • x86-64 host with a supported Linux distribution;
  • Docker Engine and Docker Compose v2;
  • Python 3.9+, curl and openssl on the host;
  • at least 8 GiB free during installation;
  • a dedicated persistent data directory;
  • an administrator-controlled backup destination;
  • DNS and TLS termination if users connect remotely.

Install the exact release:

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

For a mainland China host that cannot reach GHCR, use the release-CDN image mirror. It authenticates the same version and image before deployment:

curl -fsSL https://releases.clawuno.com/install-cn.sh | bash -s -- --version 0.8.1

The container runs as a non-root user, has no Docker socket, and stores persistent state outside its read-only program filesystem. Do not mount the host root, administrator credentials or Docker socket into Clawuno.

Connect from another computer​

The macOS and Windows apps can act as clients for a remote Engine running on macOS, Windows or Linux:

  1. open Engine connections from the app title bar or application menu;
  2. choose Add remote Engine;
  3. enter a name and the protected Engine origin, then choose Verify & connect;
  4. sign in with an account configured on that Engine.

A standard desktop or mobile browser can also open the Engine URL directly. Browser clients do not provide native Desktop Browser Tabs, native folder selection or app-managed updates.

Switching a Desktop window to a remote Engine does not move data or stop the Local Engine. Agent execution, Managed Chromium, Office processing, Workspace files and scheduled Work remain on the selected Engine host. Desktop Browser Tabs and local downloads remain on the client computer. A linked folder must therefore be accessible to the Engine host, not merely to the remote client.

Network boundary​

For every host platform, do not expose the raw Engine port directly to the public internet. For remote users:

  1. keep the Engine behind a firewall, on a private network, or reachable through a controlled tunnel;
  2. prefer HTTPS at an administrator-owned reverse proxy; a private overlay network or loopback tunnel can also provide a controlled path;
  3. forward the original public origin consistently;
  4. restrict firewall access to the intended network;
  5. test sign-in, streaming responses, file upload/download and long-running requests through the proxy.

macOS and Windows Desktop can save an explicitly entered HTTP origin, but the app warns that credentials, chats and files may be intercepted or modified. Use HTTPS for normal remote access. Do not expose port 9700 directly to the public internet.

Linked folders​

Mount only specific approved directories. A linked folder keeps its existing ownership and backup policy. Clawuno must not recursively change ownership of host data to make a mount work.

Acceptance check​

Before inviting users, verify version 0.8.1, administrator and remote-user sign-in, host restart/quit behavior, model access, Workspace and Agent creation, file upload/download, Office preview, Engine Browser, scheduled Work, and a backup stored outside the program installation. On macOS and Windows, also verify that remote access fails clearly when the host app is intentionally quit and recovers after the signed-in host user restarts Clawuno.