Installation
Install the jurniti CLI on macOS, Linux, or Windows — one line via curl or PowerShell. Skip this if you only use the web dashboard.
Install the CLI
You only need the CLI if you want a terminal, CI, scripts, or MCP. Dashboard-only users can skip this page — sign in at app.jurniti.com/login and go to Quickstart (dashboard path).
The jurniti CLI is a single static binary. Every install path lands the same
binary on your PATH.
One-line install (recommended)
macOS and Linux, x86_64 and arm64:
curl -fsSL https://jurniti.com/install.sh | shThe script detects OS and architecture, downloads the matching release, verifies
its checksum, and drops jurniti onto your PATH.
On Windows
In PowerShell (x64 or arm64):
irm https://jurniti.com/install.ps1 | iexSame idea: detect architecture, checksum-verify jurniti.exe, install under
%LOCALAPPDATA%\Programs\jurniti, and add that directory to your user PATH.
Open a new terminal so the updated PATH takes effect.
Verify
jurniti --versionmacOS, Linux & Windows
Prebuilt binaries ship for macOS (Apple Silicon + Intel), Linux (x86_64 + arm64), and Windows (x64 + arm64).
Staying up to date
Once installed, the CLI checks for new releases at most once a day and prints a
one-line notice on stderr when one exists (never in --json output, CI, or
non-interactive shells; opt out with JURNITI_NO_UPDATE_CHECK=1). Update any
time with:
jurniti upgradeReleases are checksum- and signature-verified before the binary is swapped — see Agent skills & updates for the full story.
Next: Quickstart — log in and bring a VM up (CLI or dashboard).