Usage

03 / 04

scirix-cli is built to be driven by an AI agent. The installer ships an agent skill that teaches Claude Code, Codex, and OpenCode how to authenticate, pick a namespace, and query the Reality Model on your behalf. Direct shell use works fine too — the same commands, with no agent in the loop.

Driving the CLI from an agent

After install, you can ask your agent things like:

"What's in the auth flow for this codebase?"

"List dependents of MyApp.Auth.LoginService."

"Are there any open conflict findings right now?"

The agent reads the installed skill, runs the right scirix commands, and synthesises the output. You don't have to remember subcommand shapes — the skill carries that knowledge.

Where the skill lives

The installer mirrors the bundled skill to:

OS	Path
Linux / macOS	`~/.scirix/skills/scirix/`
Windows	`%USERPROFILE%\.scirix\skills\scirix\`

It then symlinks (Linux/macOS) or junctions (Windows) that directory into each detected agent's skills location:

Agent	Linked into
Claude Code	`~/.claude/skills/scirix/`
Codex	`~/.codex/skills/scirix/`
OpenCode	`~/.config/opencode/skills/scirix/`

Because every agent points at the same source, upgrading scirix-cli upgrades the skill in every agent at once — there's no per-agent state to keep in sync.

Refreshing the link

If you install an agent after scirix, re-run the installer (or run the link step manually):

ln -sfn ~/.scirix/skills/scirix ~/.claude/skills/scirix

New-Item -ItemType Junction -Path "$env:USERPROFILE\.claude\skills\scirix" `
                            -Target "$env:USERPROFILE\.scirix\skills\scirix"

Driving the CLI directly

Everything the agent can do, you can do from the shell — useful for scripts, CI, and quick one-offs. The CLI is self-documenting:

scirix help
scirix rm --help
scirix auth --help

--help works on every subcommand, and JSON is the default output format across scirix rm so it pipes straight into jq or downstream tools.

Cloning every repo in a namespace

For the common "I'm new on this machine, give me every repo in the namespace" case:

mkdir ~/projects/acme && cd ~/projects/acme
scirix ns pull

That clones every repository registered in the active namespace into the current directory. Future runs from anywhere under the same tree do a git pull --ff-only on each repo instead. Auth (SSH keys, credential helper) is whatever your system git is configured with.