Quickstart

Change into a project — any directory inside it works, opi searches upwards for package.json and Cargo.toml — and run it:

opi

The start screen lists the project’s scripts. Enter runs the highlighted one; the cursor starts on the first entry of the first group, so opi ↵ usually starts dev.

Three speeds

All three are backed by the same task model:

opi                   # navigate: ↓ ↓ Enter
opi                   # filter:   /dep ↵
opi dev               # direct, no interface

Arguments after the name go to the script:

opi build --verbose

A literal -- before the script’s arguments is accepted and dropped, since that is the habit npm run teaches.

The script replaces opi

The script replaces the opi process. Ctrl-C reaches your dev server rather than a wrapper, and the script’s exit code is what your shell sees, so opi build && … works.

The other areas

From the list, a hotkey opens each area; on the command line it is a flag:

Key	Flag	Area
H	opi --health	Health
S	opi --security	Security
U	opi --updates	Updates
C	opi --clean	Clean
	opi --check commit	Workflows
	opi --check push	Workflows
	opi --check release	Workflows
	opi --hooks	Workflows

Never a bare word: health, clean and release are script names in real projects, and the bare word stays theirs.