---
url: https://clusto.app/docs/downloads.md
description: >-
  Download the current Clusto apps and install the CLI and daemon on a Linux
  server.
---

# Downloads & Installation

Open [clusto.app/download](https://clusto.app/download) to download the current
Clusto release. The page reads the live release manifest, selects the most likely
platform for your device, and keeps Windows, Linux, Android, iOS, and macOS tabs
available so you can choose another target.

Each available artifact is linked directly and shows its current filename and
download size. You do not need to browse the distribution server or guess which
file belongs to the latest release.

## App downloads

| Platform | Current options |
| --- | --- |
| Windows | x64 NSIS installer (`.exe`) |
| Linux | Debian / Ubuntu package (`.deb`), Fedora / RHEL package (`.rpm`), AppImage, and system tarball (`.tar.gz`) |
| Android | Universal APK |
| iOS | Installable [web app](https://web.clusto.app/) for iPhone and iPad; no public App Store download is currently available |
| macOS | No native artifact is included in the current release manifest. Use the [web app](https://web.clusto.app/) for now. |

The download page includes setup steps beside each platform. For Linux, prefer
the native package for your distribution. Use the AppImage when no package
matches your system.

On iPhone or iPad, open the web app in Safari, tap **Share**, choose **Add to
Home Screen**, and confirm **Add**. Clusto then launches from the Home Screen in
its standalone app view.

## Install the daemon separately

The app is a client for a node (a daemon) on your own machine or a remote
server. To run one on the computer you are using, use the one-click setup below.
For another machine, install the daemon with the install script and CLI wizard,
then connect to it. The app does not start, stop, or uninstall a service after
setup, and it does not bundle the CLI.

**Settings > Daemon Setup** (the Daemon setup tab) has a one-click **Set up this
computer** button on Windows and Linux, plus the Linux and Windows install
commands and a link to the download page for installing on another machine. The
F1 command **Set up Clusto on this computer** is available from anywhere in the
app, and **Daemon installation instructions** opens the same setup page.

## Set up a Linux server

One command sets up a server, the same as on Windows:

```bash
curl -fsSL https://dl.clusto.app/install.sh | sh
```

The script installs the CLI for the detected x64 or ARM64 platform, then runs
the `clusto install` wizard on your terminal, through `sudo` when you are not
root. The wizard installs the matching daemon, asks for its connection and
cluster settings, writes the configuration, and starts the service by default.
If the wizard fails, the script runs `clusto doctor` and exits with an error.

When there is no terminal, no `sudo`, or `CLUSTO_SKIP_WIZARD=1` is set, the
script only installs the CLI and prints the next step, `sudo clusto install`.
For example:

```bash
curl -fsSL https://dl.clusto.app/install.sh | CLUSTO_SKIP_WIZARD=1 sh
```

`clusto install` never creates a second daemon: on a machine that already has
`clustod` it asks before replacing the config, and on an old Hive node it
upgrades the node in place. The shell script tells you when it detects a Hive
node. Afterwards, `clusto doctor` checks the install.

### Signature verification

Every Clusto release is signed. The manifest entry for the CLI carries an Ed25519
signature from a Clusto release key, and `install.sh` has the matching public keys
built in. With **OpenSSL 3** installed, the script verifies that signature, then
checks the download's size and SHA-256 against the signed entry, and refuses to
install anything that does not verify. It downloads over HTTPS only (plain
`http://` is accepted just for a mirror on the same machine).

Without OpenSSL 3 (or with a FIPS-only OpenSSL that cannot check Ed25519), the
script warns that the signature was not verified and falls back to HTTPS plus the
manifest's SHA-256. To make that an error instead, set
`CLUSTO_REQUIRE_SIGNATURE=1`:

```bash
curl -fsSL https://dl.clusto.app/install.sh | CLUSTO_REQUIRE_SIGNATURE=1 bash
```

Once installed, `clusto` verifies the signature of every later update itself.
See [Remote-URL Updates](/remote-updates#security-model).

After installation, open **Connection** in the app and add the daemon's host,
port, and token. A daemon on the same machine connects like any other node.
Once connected, use **Cluster** to configure, restart, or update nodes over the
authenticated connection. Manage the installed service directly on its host.

## Install without sudo or administrator rights

When you cannot use `sudo` (Linux, macOS) or elevate to administrator (Windows),
install the node for your own account only:

```bash
curl -fsSL https://dl.clusto.app/install.sh | CLUSTO_SKIP_WIZARD=1 sh
clusto install --user
```

Do not run it under `sudo`. The daemon goes to `~/.local/bin` on Linux and macOS
or `%LOCALAPPDATA%\Programs\Clusto` on Windows, and uses your per-user config
(`~/.config/clusto/config.toml` on Linux). Autostart is set up for you:

* **Linux:** a systemd user unit `~/.config/systemd/user/clustod.service`, enabled,
  plus `loginctl enable-linger` so it starts at boot and keeps running after you
  log out. If lingering is refused, the daemon only runs while you are logged in,
  and the installer prints `sudo loginctl enable-linger "$USER"` for an
  administrator to run once.
* **macOS:** a LaunchAgent `~/Library/LaunchAgents/app.clusto.clustod.plist`
  that runs at login and is kept alive.
* **Windows:** a `Clusto Daemon` entry under
  `HKCU\Software\Microsoft\Windows\CurrentVersion\Run`, so the daemon starts
  when you sign in. There is no Windows service, no `clusto-runas` helper and no
  firewall rule; Windows may show its own firewall prompt the first time the
  daemon listens.

If the user manager is not reachable (for example you are not in a login
session), the installer says so and starts the daemon detached. It then does not
return after a reboot.

Limits: sessions and chats run as your account only, with no run-as for other OS
users. A machine has either a system install or a user install, never both:
`clusto install --user` refuses when a system `clustod` exists, and a plain
`clusto install` refuses when a user install exists (remove it with
`systemctl --user disable --now clustod`). Self-update, restart and
[terminals that survive a restart](/remote-updates#terminals-that-survive-a-restart)
work under the user manager. `clusto doctor` shows the Linux unit as
"clustod user service".

## Set up this computer from the app

On Windows and Linux, the desktop app can set up a node on the PC it runs on and
connect to it in one step. When the app is disconnected and no node runs on this PC,
the Connect view shows a **Set up Clusto on this computer** card (also in the F1
palette as **Set up Clusto on this computer**). Press its button. The app picks
[local mode](#local-mode-a-node-inside-the-app) when its installer bundles the
Clusto CLI, which is the case for every released desktop installer. A build without
the bundled CLI (a development build) uses the system install below instead.

### System install (builds without the bundled CLI)

1. The OS asks for administrator rights once. On Windows that is a UAC prompt, then an
   installer window that shows progress, closes itself on success and waits for Enter on
   failure. On Linux it is the graphical pkexec (polkit) prompt.
2. The app makes a single-use pairing code (valid 24 hours) and hands it to the
   installer through an owner-only temporary file, so you never copy a code.
3. The installer sets up the node as a background service. The app waits for it to
   answer, pairs with it, saves a profile named after the machine (the default profile
   when you have none, loopback address first) and connects.

On Linux without pkexec or without a polkit agent, the card shows a command to paste into
a terminal instead, and connects by itself once the node is up:

```bash
curl -fsSL https://dl.clusto.app/install.sh | CLUSTO_SKIP_WIZARD=1 bash && sudo /usr/local/bin/clusto install --non-interactive --pairing-code-file '<path>'
```

If a node already runs on this PC but no saved profile reaches it, the card offers
**Connect** instead. It opens Add Profile prefilled with the address and node identity;
enter a pairing code or the token (`clusto daemon get-token`).

A first run with no saved profiles asks the question in
[First launch](#first-launch-simple-or-advanced) first. The flow is not offered on macOS, which has no node build. The
Windows script reads the code file from `CLUSTO_PAIRING_CODE_FILE` (the app sets it) and
runs `clusto install --non-interactive --pairing-code-file`.

## Local mode: a node inside the app

The Windows and Linux desktop installers bundle the `clusto` CLI, which carries the
Clusto node (`clustod`). Choosing **Simple** on the first-launch screen, or pressing
**Set up Clusto on this computer** on the Connect view, sets up a node that runs
inside the app itself:

* Nothing is installed system-wide. There is no administrator, UAC or pkexec prompt
  and no download, so it works offline.
* The app pairs with the node automatically and saves a **This computer** profile,
  the same as the system install.
* The node lives in the app's local data folder under `local-node`: `bin/` (its copy
  of the CLI), `config/config.toml` and `data/`.
* It listens on loopback only (`127.0.0.1`), on port 9178 or the first free port in
  9180-9500, and runs standalone, with no cluster. To use this computer in a cluster,
  connect to or install a regular node instead.
* It starts when the app starts and stops when you quit the app. Terminal sessions
  keep running in their holder processes while it is stopped and reattach on the next
  start (see [terminals that survive a restart](/remote-updates#terminals-that-survive-a-restart)).
  If it crashes it restarts by itself; after 5 exits within 2 minutes the app stops
  trying and shows the node as stopped.
* It updates together with the app. The node update screen refuses to update it and it
  never polls for updates; after an app update, the next start refreshes the node to
  the new version.

In **Settings**, the node card **Clusto node on this computer** shows it as **Run by
this app** with **Start**, **Stop** and **Restart** buttons, and none of them asks for
administrator rights.

Local mode is available in the Windows and Linux desktop apps only; the mobile apps,
the web client and macOS do not have it. It is free on every plan. To run the node
independently of the app (always on, at boot, or shared with other devices), use the
[system install](#system-install-builds-without-the-bundled-cli) or the
[install script](#set-up-a-windows-machine) instead.

## First launch: Simple or Advanced

The first time the desktop app starts without a saved connection, it opens a
**Welcome to Clusto** screen and asks how you want to use Clusto on this
computer. You can change the choice later.

* **Simple** (this computer only) - sets up Clusto on this computer with
  [local mode](#local-mode-a-node-inside-the-app) and connects to it. Navigation shows Terminals, Chats
  and Notes. If Clusto already runs here, the screen offers to connect to it
  with its pairing code or token instead.
* **Advanced** (cluster and remote nodes) - opens the Connect view to connect to
  a server, scan your network and add more machines. Navigation shows every
  feature.

The `F1` palette has **Use Simple local mode** and **Show advanced setup** to
switch later; see [Appearance](/appearance#navigation-profiles-and-density) for
the navigation profiles. After the first connect, a short
[glossary of Clusto terms](/concepts) opens once.

## Set up a Windows machine

Open PowerShell and run:

```powershell
irm https://dl.clusto.app/install.ps1 | iex
```

The script asks for administrator rights once (setup continues in a new
window), downloads the Clusto CLI, checks its SHA-256 against the release
manifest, installs it to `C:\Program Files\Clusto`, adds that folder to `PATH`,
and starts the same `clusto install` wizard. The wizard installs the daemon as
the `clustod` Windows service, which starts at boot. If the install fails, the
script runs `clusto doctor` and points you to `clusto doctor --fix`, which
repairs what it can from an Administrator terminal.

Windows PowerShell cannot verify Ed25519 signatures, so this first download is
trusted through HTTPS and the manifest's SHA-256 only. Once installed, `clusto`
verifies the release signature of every later update. Downloads are HTTPS only;
plain `http://` is accepted for a loopback test mirror and nothing else.

When it finishes, open a new terminal and run `clusto daemon get-token` to get
the token for the app's **Connection** screen.

See the [`clusto install` CLI reference](/cli#clusto-install-install-the-daemon)
for every option, including non-interactive installation. See
[Remote-URL Updates](/remote-updates) for the release manifest, checksums, and the
update flow after installation.
