Install the laptop client
The first client distribution supports macOS and Linux with Node.js 24+ and curl. It is a portable JavaScript bundle; no npm global install, repository clone or server credential is needed.
Install
Run as your normal development user, without sudo:
node --version
curl -fsSL https://devbox.508.dev/install.sh | sh
devbox --helpNode.js is a prerequisite, not downloaded by this installer. Install a supported runtime from Node.js or your existing version manager, then rerun the command.
To inspect before running, download the script and read it locally:
curl -fsSL https://devbox.508.dev/install.sh -o install-devbox.sh
less install-devbox.sh
sh install-devbox.shWhat changes
- Client files go under
$XDG_DATA_HOME/508-remote/client, or~/.local/share/508-remote/client. - A launcher is linked from
~/.local/bin/devbox. - The launcher defaults to the control plane that distributed it.
FIVE08_REMOTE_API_URLoverrides that default. - Shell profiles, global SSH configuration, vendor authentication and project files are not edited.
The installer prints a PATH command if needed. Persist that PATH entry yourself in the startup file for your shell. FIVE08_REMOTE_BIN_DIR selects another user-owned bin directory when explicitly set.
export PATH="$HOME/.local/bin:$PATH"Verification and trust
The HTTPS bootstrap contains the exact size and SHA-256 of each content-addressed client file. All downloads are checked before the bundled CLI is executed. Installation stages the complete client, runs its help self-check, then switches the current release.
This trusts the HTTPS origin supplying the installer. Embedded digests protect against damaged or mismatched downloads; they are not an independent signing authority if that origin itself is compromised. The privileged host updater has a separate pinned signing-key boundary, which this client installer does not replace.
The installer refuses root, unsafe installation paths and an existing unrelated devbox command in its destination. A failed download or self-check leaves the previous client active. An abandoned install lock requires inspection before manual removal.
Update and recover
Rerun the installer to install the current deployed client. It keeps content-addressed releases for explicit recovery; it does not run an automatic background updater. Previous releases occupy disk until you remove ones you no longer need.
The launcher uses the verified Node executable present at install time. If a version manager removes that runtime, activate Node.js 24+ and rerun the installer.
An old installer can refer to files no longer served after a deployment. Download a fresh installer and retry; never disable integrity checks to work around a 404.
Uninstall
Remove the devbox symlink and the dedicated client directory after checking their paths. Keep ~/.config/508-remote if you want to retain saved connections and credentials. The installer never removes those credentials on your behalf.
Other deployment origins
Operators build their own distribution with FIVE08_REMOTE_INSTALL_ORIGIN. If using a separately trusted download origin, set FIVE08_REMOTE_DOWNLOAD_ORIGIN for that install. HTTPS is required; this option is not a way to disable verification.
Native Windows installation, bundled Node runtimes, package-manager taps and independently signed laptop binaries are future distribution work. WSL can use the Linux path, with its own SSH and editor configuration.