CLI¶
One page per command of Nullius's shell interface; --help on any command gives its arguments.
After installation, use nullius from any directory.
python -m nullius is identical when that Python environment contains Nullius.
An installation made by uv tool install has its own interpreter: use its
nullius command, not an unrelated system Python.
From a source checkout, replace nullius with
PYTHONPATH=app python3 -m nullius. To serve from source with Flask, the existing
uv run --no-project --with-requirements app/requirements.txt app/app.py command
also works.
| Page | Command |
|---|---|
| Launch | nullius serve [roots...] |
| Read jobs | nullius runs, nullius compare, nullius workspace, nullius standard traces |
| Import a run | nullius import |
| Definitions | nullius standard list, check, fit, new |
| Run a benchmark | nullius standard run |
| Prove a benchmark | nullius standard prove |
| Conform an agent or a capability | nullius standard conform |
| Fidelity | nullius standard fidelity |
| Shard and merge | nullius standard run --shard, merge |
| Storage | nullius paths [--json] |
| Migration | nullius migrate --from CHECKOUT [--secrets PATH] [--apply] |
| Pages from a shell | |
| Exit codes and output |
A Harbor recipe runs by its generated script, not a command: Run builder.
The module CLIs remain available from an installed interpreter or with
PYTHONPATH=app in a checkout. The unified command loads saved settings;
standard --from-run uses only the supplied run environment.