> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cyberun.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# Download and install

> Get the standalone agent and the Cyberun CLI for your operating system.

Two pieces of Cyberun ship to your machine:

* **Cyberun Agent** — the standalone, headless agent. Runs as a
  system service on a dedicated GPU host (a desktop, a
  workstation, or a server).
* **Cyberun CLI** — the `cyberun` command-line tool. Drive your
  team's workflows from a terminal, script them in CI, or share a
  local GPU with `cyberun agent serve`.

A team running its own GPU servers installs the agent on those
servers. Developers who live in the terminal install the CLI.

## Cyberun Agent (headless agent)

Install on a Linux, macOS, or Windows host that has a usable GPU.
The agent runs on all three; which runtimes you can run is set by
each runtime, not by the agent (see
[Platform → Agents](/platform/agents)).

### Linux & macOS one-liner

```sh theme={null}
curl -sL https://releases.cyberun.cloud/agent/install.sh | bash -s -- \
    --api-key ak-…
```

The default install is rootless — no `sudo`, and comfyui is the
default tool. The script downloads the right binary for
`linux-amd64`, `linux-arm64`, `darwin-amd64`, or `darwin-arm64`,
sets up the runtime under `~/.cyberun/agent/<tool>`, registers a
per-user service (user systemd, or launchd on macOS), and starts
it.

For Docker mode, Nerfstudio, and the full flag list see
[Connect an agent](/cloud/guides/connect-agent) and
[Platform → Agents](/platform/agents).

### Windows one-liner (PowerShell)

```powershell theme={null}
& ([scriptblock]::Create((irm https://releases.cyberun.cloud/agent/install.ps1))) -ApiKey ak-…
```

### Direct binary downloads

The installer is the recommended path. If you need the bare
binary (offline transfer, custom packaging), pull it directly:

| Platform    | Architecture  | Binary                                                                                             |
| ----------- | ------------- | -------------------------------------------------------------------------------------------------- |
| **Linux**   | x86-64        | [`cyberun-agent`](https://releases.cyberun.cloud/agent/linux-amd64/latest/cyberun-agent)           |
| **Linux**   | ARM64         | [`cyberun-agent`](https://releases.cyberun.cloud/agent/linux-arm64/latest/cyberun-agent)           |
| **macOS**   | Apple Silicon | [`cyberun-agent`](https://releases.cyberun.cloud/agent/darwin-arm64/latest/cyberun-agent)          |
| **macOS**   | Intel         | [`cyberun-agent`](https://releases.cyberun.cloud/agent/darwin-amd64/latest/cyberun-agent)          |
| **Windows** | x86-64        | [`cyberun-agent.exe`](https://releases.cyberun.cloud/agent/windows-amd64/latest/cyberun-agent.exe) |
| **Windows** | ARM64         | [`cyberun-agent.exe`](https://releases.cyberun.cloud/agent/windows-arm64/latest/cyberun-agent.exe) |

The bare binary expects a `cyberun-agent.yaml` config file (the
installer generates this for you). To roll your own config, start
from the template the installer writes — see
[Platform → Agents](/platform/agents).

### Agent verification

```sh theme={null}
# Checksums for binaries and install scripts under agent/
curl -sL https://releases.cyberun.cloud/agent/checksums.txt
```

## Cyberun CLI

The `cyberun` CLI ships on its own release track, separate from
the agent. Install it on Linux, macOS, or Windows.

<CodeGroup>
  ```bash Linux / macOS theme={null}
  curl -sL https://releases.cyberun.cloud/cli/install.sh | bash
  ```

  ```powershell Windows theme={null}
  & ([scriptblock]::Create((irm https://releases.cyberun.cloud/cli/install.ps1)))
  ```
</CodeGroup>

Point it at the Cloud API once, then sign in:

```bash theme={null}
export CYBERUN_API_URL=https://core.cyberun.cloud
cyberun auth login
```

Prefer the bare binary? Builds are published per platform under
`releases.cyberun.cloud/cli/<os>-<arch>/latest/`, with a single
shared `cli/checksums.txt`, for Linux, macOS, and Windows on
`amd64` and `arm64`. Pin a build by swapping `latest` for the
version number.

The full command reference — `auth`, `run`, `workflow`, `task`,
and `agent serve` — is in the [CLI guide](/cloud/guides/cli).

## After you install

Either path lands you in the same place:

<CardGroup cols={2}>
  <Card title="Cloud → Run your first task" icon="play" href="/cloud/getting-started/first-task">
    Step-by-step: create a team, connect an agent, submit a task.
  </Card>

  <Card title="Connect AI clients" icon="plug" href="/cloud/guides/connect-mcp">
    Drive Cyberun from Claude Code, Cursor, or any MCP client.
  </Card>
</CardGroup>

## Update channels

Stable releases land under `/latest/`. Older versions stay live
forever under their version number, so an old install link keeps
working — there is no release pruning. The pre-release stream
(beta/RC) is not exposed via `/latest/`; ask in your team's
support channel for early access.

## Reporting a problem

* **Agent install script fails** —
  [Connect an agent → Troubleshooting](/cloud/guides/connect-agent#troubleshooting).
* **Anything else** — `sales@cyberun.cloud`.