CLI reference¶
Every krites command. krites <command> --help is always authoritative for the
flag set of the binary you are running; these pages add the defaults, the failure
modes, and what each command writes to disk.
Shoot pipeline commands¶
Run in roughly this order over a single shoot.
| Command | Description |
|---|---|
| ingest | Register a folder of frames as a shoot workspace |
| cull | Judge a shoot — analyse frames and assign keep/maybe/reject verdicts |
| dedup | Report the near-duplicate burst clusters in a culled shoot |
| verdict | Override a frame's verdict (keep, maybe or reject) |
| straighten | Detect and propose a level correction for keeper frames |
| crop | Propose a composition crop for keeper frames |
| develop | Apply a look to keeper frames |
| remove | Remove an object from a frame by inpainting a masked region |
| review | Get an AI critique of selected frames (never affects the cull) |
| export | Render the chosen verdict set into the shoot's export/ directory |
| xmp · xmp write | Write Lightroom XMP sidecars beside the originals |
Recovery commands¶
| Command | Description |
|---|---|
| reset | Return a shoot, its exports, or one frame to a known state |
| reset frame | Reset one frame to its post-ingest state |
| reset shoot | Reset a whole shoot toward its post-ingest state |
| reset exports | Delete everything under the shoot's export/ directory |
Studio commands¶
| Command | Description |
|---|---|
| studio | Start the local studio web UI |
| launch | Open the studio (starting it if needed) and open the browser |
Installation and configuration commands¶
These come from go-tool-base, the framework krites is built on, and behave the same way in every tool built on it.
| Command | Description |
|---|---|
| init | Write the configuration file and run first-run bootstrap |
| config | Read, write, validate and locate configuration values |
| update | Update the running binary to the latest signed release |
| version | Print version, commit and build date |
| doctor | Check environment and configuration health |
| changelog | Show version history, embedded at build time |
| docs | Browse the embedded documentation in the terminal |
| mcp | Expose krites' commands as MCP tools for an AI assistant |
krites completion <shell> generates a shell completion script. It takes no
krites-specific options; krites completion --help documents it.
Flags every command accepts¶
--config, --debug, --ci and --output are registered on the root command,
so they work on every subcommand. See Global flags.
Commands gated off the MCP tool surface¶
An AI agent driving krites over MCP sees a deliberately reduced tool set. Anything that produces pixels, egresses an image, or destroys work is excluded:
| Excluded | Why |
|---|---|
export, remove, xmp write |
they produce pixels, or write into your original folder |
review |
it sends the image to a third-party model |
studio, launch |
they start a long-running server and open a browser |
reset frame, reset shoot, reset exports |
they delete work, with no confirmation prompt |
Everything else — ingest, cull, dedup, verdict, straighten, crop,
develop — is available to an agent, because each only ever writes a reversible
record.
Where configuration lives¶
Provider configuration, cull-profile thresholds and their defaults are in the configuration reference.