Installation

jrt is a single self-contained binary. Install it once; it manages everything else itself.

One-line install

The installer detects your OS and CPU, downloads the matching binary from runtime.jervis.cloud, verifies its SHA-256 checksum against SHA256SUMS, and places it at ~/.jrt/bin/jrt. It refuses to install a file whose checksum does not match.

PowerShell

irm https://runtime.jervis.cloud/install.ps1 | iex

Add jrt to your PATH

The installer prints this hint if ~/.jrt/bin is not on your PATH yet. You only do it once.

PowerShell

[Environment]::SetEnvironmentVariable('Path', "$HOME\.jrt\bin;" + [Environment]::GetEnvironmentVariable('Path','User'), 'User')
# then open a new terminal

Verify

shell

jrt version
jrt doctor

jrt doctor reports the backend, registry and shim state. On a fresh machine it shows mise: missing with the fix jrt backend bootstrap — that is expected; the Quick start covers it.

Installer options

Variable	Default	Purpose
`JRT_VERSION`	`latest`	Release tag to install, e.g. `v0.1.0`.
`JRT_INSTALL_DIR`	`~/.jrt/bin`	Where the binary is placed.
`JRT_RELEASE_URL`	`https://runtime.jervis.cloud/dl/latest`	Alternate base URL (a mirror or local folder) holding the binaries and `SHA256SUMS`.

PowerShell

$env:JRT_VERSION = 'v0.1.0'
irm https://runtime.jervis.cloud/install.ps1 | iex

Manual download

Every release is served from https://runtime.jervis.cloud/dl/v<version>/, with /dl/latest/ pointing at the newest one. Each holds jrt-<os>-<arch> binaries for windows, linux and darwin on amd64 and arm64, plus SHA256SUMS. Download the one for your platform, verify it, rename it to jrt (jrt.exe on Windows) and put it on your PATH.

shell

base=https://runtime.jervis.cloud/dl/v0.1.0
curl -fsSLO "$base/SHA256SUMS"
curl -fsSLO "$base/jrt-linux-amd64"
sha256sum -c SHA256SUMS --ignore-missing

Build from source

shell

git clone https://github.com/keroloszakaria/Jervis-Runtime
cd Jervis-Runtime
go build -o jrt ./cmd/jrt          # Go 1.27+

Supported platforms

OS	Architectures	Notes
Windows 10/11	amd64, arm64	Shims are hard links of `jrt.exe` — no `.cmd` wrappers.
Linux (glibc)	amd64, arm64	Verified end to end on Debian.
Linux (musl)	amd64, arm64	Alpine and other musl hosts get the static musl backend automatically.
macOS	Intel, Apple Silicon	Uses the same path as Linux.

Uninstall

Delete the binary (~/.jrt/bin/jrt) and, if you also want to remove every runtime and tool jrt installed, delete JRT_HOME (run jrt storage to see where it is). If you enabled shims, remove the shim directory from your PATH first.