Before you install
- A Cyberun team and an agent credential (
ak-...) for that team. Create one from Access → Agent in Cyberun Cloud. - A GPU suited to the runtimes you’ll run, plus disk for their model caches. The agent runs on Linux, macOS, and Windows; a runtime’s availability is set by that runtime, not by the agent. Nerfstudio, for example, needs Linux + NVIDIA, while ComfyUI also runs on macOS (Apple GPU via Metal) and Windows.
- Outbound network access from the host to your Cyberun gateway. Agents do not need an inbound listener.
Linux and macOS
sudo. The shared agent
binary lands in ~/.cyberun/bin, each tool’s runtime in
~/.cyberun/agent/<tool>, and the agent runs under a per-user
service: user systemd on Linux, a launchd user agent on macOS. You
only need sudo for --system or --docker, or to let the
installer pull system prerequisites (NVIDIA driver, missing apt
packages). On Linux, run sudo loginctl enable-linger <user> so the
per-user agent keeps running after logout and starts at boot.
Omit --api-key and the installer prompts for the credential
interactively (hidden input). Passing the credential on the
command line is best reserved for automation that already keeps
it in a secret manager.
Windows (PowerShell)
%USERPROFILE%\.cyberun\bin and runs under a
per-user Scheduled Task that starts at logon. comfyui is the only
Windows runtime and the default, so -Tool can be omitted.
Install flags
To point the agent at a non-default gateway, set
CYBERUN_WSS_URL=wss://... in the install environment (Linux,
macOS) or pass -GatewayUrl wss://... (Windows).
Uninstall flags
Where the agent lives
The default rootless install lays out like this:
A
--system install on Linux lives under /opt/cyberun instead,
with a root systemd unit you read via
journalctl -u cyberun-agent-<tool>.
One install = one tool runtime = one agent process. The shared
agent binary is reused; each tool gets its own
~/.cyberun/agent/<tool> directory and its own service. To run
ComfyUI and Nerfstudio on the same Linux box, run the installer
once per tool.
After install
Once the service starts, the agent dials the gateway, presents its agent credential, and reports its labels and capabilities. The team’s Cyberun Cloud dashboard shows the agent under Agents within a few seconds. From there, tasks the agent is eligible for can be dispatched to it. The eligibility model is covered in Cloud → Agents.Updating the agent
Re-run the installer for the same tool. It drops in the new binary and re-applies the service definition; settings and model caches are preserved. On macOS the launchd agent reloads immediately; on Linux restart the service to pick up the new binary —systemctl --user restart cyberun-agent-<tool> (or systemctl restart for a
--system install).
Removing the agent
Run the uninstall command shown above. Without--purge, the
ComfyUI checkout and models stay on disk in case you reinstall
later; with --purge, everything under the install directory is
removed.