Chapter 23 — CLI Reference
Command Line
The top-level iris command launches the bench dashboard. It also carries
four things that launch nothing: a license preflight, two registry commands,
and the installation verifier.
iris [<run-dir>] [flags...] Launch the bench dashboard. Daemonizes by
default; -f/--foreground stays attached.
Flags: --port N, --no-open/--no-browser,
--replay.
iris smoke [--dryrun] [--yes] Verify this installation end to end.
--dryrun is the zero-credit wiring and
license-reachability check; --yes skips
the cost-disclosure prompt (full mode).
iris open Open a browser tab on every bench running
on this machine.
iris stop [<run-dir>] Stop the bench(es) registered for a run
dir (default: the current directory).
iris --license Check the license server (alias
--license-check); nonzero exit if it is
not ready. Places no hold, spends nothing.
iris balance Print the pool balance, in credits.
No run dir needed; nonzero exit if there
is no license or the server can't be
reached.
iris --help Top-level usage and flags.
It is covered in Bench:
point it at a run directory holding the inline tracker's output and it reads
the *.iris bundle there (single-stem: <basename(run-dir)>.iris; several
bundles and no tracker writing → the most recently written one, named in the
startup banner; none at all → it starts anyway with a Navigator), computes
every diagnostic live, and
generates the PDF report from its Export as PDF button. The bundle is the only
data input — the bench never reads sibling training logs, step-shard
directories, or any other file for its diagnostics.
There is no separate command that produces a bundle, and no separate command that produces a report. Bundles come from the inline tracker running inside your training script (Chapter 9) — IRIS™ measures a training run from the inside — and the bench is then opened on the run directory.
analyze and extract are not commands: the launcher
If the smoke test reports insufficient available memory, close other applications or use an appropriate machine before retrying. Read the reported cause; do not treat a refused verification as a successful install.
