Install
01 / 05
scirix-cli is a single static binary. There is no package manager
dependency, no runtime, and no daemon. The recommended install path is
the one-liner — but every step can be done manually instead.
One-line installers
curl -fsSL https://cli.scirix.fi/install.sh | sh
irm https://cli.scirix.fi/install.ps1 | iex
The script picks the right archive for your OS and architecture
(amd64 or arm64), verifies the SHA-256 checksum, and drops the
binary into a sensible install dir.
| Platform | Default install dir |
|---|---|
| Linux, macOS | /usr/local/bin if writable, otherwise ~/.local/bin |
| Windows | %LOCALAPPDATA%\scirix\bin (added to your user and current PATH by default) |
Windows desktop PATH refresh
The installer adds the binary directory to your user PATH by default,
updates the installing PowerShell session, and broadcasts
WM_SETTINGCHANGE("Environment") to desktop applications. This lets Explorer
refresh the environment inherited by newly launched apps, without restarting
Windows. The notification also runs on reinstalls when the directory is already
on the user PATH, repairing a stale desktop environment.
Fully close and reopen applications that do not reload their environment; check for tray/background instances too. A new terminal tab can still inherit the existing terminal process's old PATH. Apps launched from the installing PowerShell session inherit its updated PATH immediately. The installer does not kill apps, restart Explorer, or modify the machine-wide PATH. If environment notification is blocked or times out, it prints a warning.
To opt out, download the script and run install.ps1 -NoAddToPath (or
-AddToPath:$false). Existing -AddToPath commands remain valid.
Pinning a version
Pass --version vX.Y.Z (Linux / macOS) or -Version vX.Y.Z (Windows) to
install a specific tag instead of the latest:
curl -fsSL https://cli.scirix.fi/install.sh | sh -s -- --version v1.2.3
irm https://cli.scirix.fi/install.ps1 | iex -Version v1.2.3
Custom install directory
curl -fsSL https://cli.scirix.fi/install.sh | sh -s -- --bin-dir ~/.local/bin
.\install.ps1 -BinDir 'C:\tools\scirix' -AddToPath
Agent skill
scirix-cli is built to be driven by an AI agent. The installer ships
an agent skill at ~/.scirix/skills/scirix/ (or
%USERPROFILE%\.scirix\skills\scirix\ on Windows) and auto-detects any
installed agent — Claude Code, Codex, GitHub Copilot, Gemini CLI,
Grok Build, Hermes Agent, JetBrains Junie, Kimi Code CLI, Kiro (CLI
and IDE), Kiro Crew, Qwen Code, Pi, OmO Native, OpenCode, OpenClaw — symlinking the
skill into each so they share one source of truth (OpenClaw and Kiro
Crew get a copy instead: they only follow skill links that stay
inside their skills root).
Override the autodetection with --agent (or -Agent on Windows):
curl -fsSL https://cli.scirix.fi/install.sh | sh -s -- --agent claude
.\install.ps1 -Agent codex
Values: claude, codex, copilot, gemini, grok, hermes,
junie, kimi, kiro, kirocrew, qwen, pi, omo, opencode,
openclaw, all, none. omo means OmO Native; omo-native aliases
omo, while omo-opencode and oh-my-opencode alias opencode. Aliases do
not cause duplicate installs or detection entries. kiro covers both Kiro
CLI and Kiro IDE (they share ~/.kiro). To skip the skill install entirely, pass --no-skill
(-NoSkill).
See Usage for what the skill actually does once it's linked.
Pi and OmO Native locations
The global skill links into <agent-dir>/skills/scirix. Pi uses
PI_CODING_AGENT_DIR or ~/.pi/agent (leading tilde expanded). OmO uses the
first nonblank trimmed OMO_CODING_AGENT_DIR, SENPI_CODING_AGENT_DIR,
PI_CODING_AGENT_DIR, or ~/.omo/agent; overrides resolve absolutely.
OmO's default home uses HOME, then USERPROFILE, then OS home even on
Windows. Use expanded absolute OmO paths and the same environment for
install and host startup. Detection checks the engine-state directory,
not PATH or ambiguous ~/.omo/omo.jsonc product settings.
Unix symlinks/Windows junctions fall back to owned copies. Existing links
to the shared mirror are reused, including coincident roots; foreign
same-name paths are preserved. Copies carry .scirix-managed-copy so only
owned copies refresh. The extensions, unlike shared skill links, need
separate Pi and OmO roots when both hosts are enabled.
Agent hooks
Alongside the skill, the installer registers a preprompt hook in each detected agent. Before every user prompt is processed, the hook hands the prompt to scirix, which consults the Reality Model for the active namespace and returns a context bundle for the agent to read alongside the prompt — relevant source-code chunks, linked documentation, neighbouring symbols, and dependency edges that touch the apparent target. The agent starts with that grounding already in context, so it does less Reality-Model querying of its own to get oriented — fewer tool calls, faster first response.
The installer wires this up automatically for every detected agent —
where each agent's hook file lives and any per-agent setup notes are
catalogued in Advanced.
Pi/OmO use generated TypeScript extensions for user-prompt context and
agent_settled improvement uploads. Start a new host session or reload
resources after install; scirix does not grant project trust or enable
user-disabled extensions/skills. Baselines checked are Pi 1.2.0 and OmO
Native 5.1.33 (pinned senpi 2026.10.13). Actual Pi loader/ExtensionRunner
trust/discovery smoke passed; no paid/model run was made. OmO remains
typecheck/stub-tested only (runtime import blocked by missing pinned
@earendil-works/chord 0.99.1), not live runtime proof.
Manage the hooks any time:
scirix hooks install # register into every detected agent
scirix hooks status # show which agents have the hook
scirix hooks uninstall # remove
Upgrading
Once scirix is installed it watches for new releases itself. On every
invocation it does a quick check against cli.scirix.fi (24-hour cache,
3-second timeout); when a newer build is published it either prompts
you in interactive shells or prints a one-line notice in scripted
contexts:
A new version of scirix is available.
Install now? [y/N]:
Type y and the binary downloads, verifies, and installs the update in
place. The bundled agent skill updates along with it — every agent
linked to it gets the version that matches the new binary. Or run the
update on demand any time:
scirix update # install latest
scirix update --version vX.Y.Z # pin a specific tag
To silence the check entirely (CI runners, locked-down environments),
set SCIRIX_NO_UPDATE_CHECK=1 in your environment.
What changed?
After an update, the next scirix invocation prints a short "What's
new" list — a feature-level summary of what changed between the version
you were on and the one you just installed. The list is generated by an
LLM from the actual code changes and is labeled (AI-generated).
It prints once, to stderr, and never blocks or delays your command.
You can also ask for it any time:
scirix changelog # most recent changes
scirix changelog --since v1.4.0 # everything after that release
scirix changelog --since 2026-08-01 # everything after a date
Full option list
The full option list is documented in the script header — fetch it with
curl -fsSLO https://cli.scirix.fi/install.sh to read locally before
running.
Manual download
Archives are served directly under https://cli.scirix.fi/releases/.
The version is in the filename:
https://cli.scirix.fi/releases/scirix-cli_X.Y.Z_linux_amd64.tar.gz
https://cli.scirix.fi/releases/scirix-cli_X.Y.Z_darwin_arm64.tar.gz
https://cli.scirix.fi/releases/scirix-cli_X.Y.Z_windows_amd64.zip
For convenience, the latest build is aliased under /releases/latest/
with the version stripped from both the path and the filename — each
URL there redirects to the matching versioned file:
https://cli.scirix.fi/releases/latest/scirix-cli_linux_amd64.tar.gz
https://cli.scirix.fi/releases/latest/scirix-cli_windows_amd64.zip
https://cli.scirix.fi/releases/latest/checksums.txt
Download, extract, drop scirix (or scirix.exe) on your PATH.
Confirm the install
scirix --version
Should print the tag, commit, and build date. If it does, move on to logging in.