CLIO Coder

Install on a cluster

Read the full guide
On this pageInstall without root Work on the cluster Old glibc, proxies, and quotas Verified downloads Airgapped sites and your own Node Related tutorials and research

Install on a cluster

Install CLIO Coder on a login node with an old glibc, a proxy, or no internet.

Install without root

The installer brings its own Node.js, so you do not need module load nodejs or a system Node. It never uses sudo and refuses to run under it.

Shell

curl -fsSL https://coder.iowarp.ai/install.sh | sh
export PATH="$HOME/.local/bin:$PATH"
clio-coder doctor

It needs curl or wget, tar with xz or gzip, and a SHA-256 tool. The runtime and package go under ~/.local/share/clio-coder-install and the launcher under ~/.local/bin. Compute nodes that mount the same home directory run the same launcher.

Work on the cluster

Ask for scheduler work in words, such as "submit job.sh and tell me when it starts". sbatch, squeue and the other Slurm, PBS, LSF and Flux clients run outside the sandbox with the same review as ssh: the safety judge decides first and asks you when it has no verdict, so name the action you want. Run them directly, not from a wrapper script, which stays inside the sandbox and fails.

Shell commands write to the project and temp folders without asking. Add scratch space with an absolute path:

YAML

safety:
  scratchRoots: [/scratch/alice]

Keep results out of Git with clio-coder store put results run-042.h5; every checkout of the project on this host sees them.

Old glibc, proxies, and quotas

The installer picks a Node build for the host. Official builds cover Linux with glibc 2.28 or newer, macOS, and Alpine on x64. An unofficial build covers x64 hosts with glibc 2.17 to 2.27, the RHEL and CentOS 7 class. Linux arm64 with an older glibc has no build; use conda-forge Node and npm instead.

Export https_proxy before running the installer behind a proxy. Node adds about 210 MB to a version, and the optional Claude Agent SDK is about 224 MB. The installer refuses to start with under about 732 MB free at the install root. On a small home quota, move the install root:

Shell

curl -fsSL https://coder.iowarp.ai/install.sh | sh -s -- --install-dir /project/$USER/clio-coder

Verified downloads

Every Node download is checked against its release SHASUMS256.txt, and a mismatch stops the install. When gpgv or gpg is present, the installer also verifies the OpenPGP signature on official builds, and it stops when nodejs.org serves no signature or a key outside the Node.js release keyring signed it.

A mirror without a signature file still installs on the checksum. Set CLIO_CODER_REQUIRE_SIGNATURE=1 to fail when no signature verifies.

Airgapped sites and your own Node

Point CLIO_CODER_NODE_MIRROR at a mirror laid out like nodejs.org/dist, CLIO_CODER_NODE_UNOFFICIAL_MIRROR at one for the glibc 2.17 build, and npm_config_registry at a registry mirror for the package's dependencies. A Node mirror can be a file:// URL on a shared filesystem.

If the site already provides Node 22.19 or newer, you can install with its npm instead: npm install -g @iowarp/clio-coder. When an older node comes first on PATH, set CLIO_CODER_NODE to the newer binary.

Pick versions with --version or --channel, and undo an upgrade with --rollback. The full guide covers the mirror variables; sh install.sh --help lists every option.