Skip to main content
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).

​
Linux & macOS one-liner

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 and Platform → Agents.

​
Windows one-liner (PowerShell)

​
Direct binary downloads

The installer is the recommended path. If you need the bare binary (offline transfer, custom packaging), pull it directly: 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.

​
Agent verification

​
Cyberun CLI

The cyberun CLI ships on its own release track, separate from the agent. Install it on Linux, macOS, or Windows.
Point it at the Cloud API once, then sign in:
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.

​
After you install

Either path lands you in the same place:

Cloud → Run your first task

Step-by-step: create a team, connect an agent, submit a task.

Connect AI clients

Drive Cyberun from Claude Code, Cursor, or any MCP client.

​
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