Updating Yokai

Yokai has two update scopes: the local release pair (yokai and yokai-tui) and the agent binary installed on each GPU device.

Upgrade the local release

yokai upgrade

The upgrader follows GitHub’s latest-release redirect, downloads the platform archive, extracts both binaries, backs up the installed files, replaces them, fixes executable permissions, and rolls back the controller if sidecar installation fails.

Restart Yokai after a successful self-upgrade.

Re-run the installer

The install command is also safe for upgrades:

curl -fsSL https://raw.githubusercontent.com/spencerbull/Yokai/main/install.sh | sh

When it finds a running daemon, the installer stops the old process and starts the freshly installed binary unless it is running through a root/sudo context where ownership would be unsafe.

Upgrade remote agents

Open Devices and use:

• U to upgrade the selected device;
• Shift+U to upgrade every configured device.

The daemon connects over SSH, replaces the agent, restarts its service, restores the tunnel, and reports per-device results.

The CLI bootstrap command can also reinstall or upgrade one device:

yokai devices bootstrap gpu-box-01

Verify versions

yokai version
yokai devices test gpu-box-01

The agent /health response includes its version. If the TUI reports route-not-found errors after an upgrade, an older daemon is probably still bound to port 7473; restart it before debugging the UI.