CLI reference¶

Every command, grouped by verb. Each page lists the flags, the defaults and the errors you get when a value is wrong. keryx <command> --help is always the authoritative, build-current flag set; these pages add the behaviour --help has no room for.

Exit codes¶

The distinction is there so a script does not have to read stderr to know what to do next. 2 means edit something and re-run; 1 means the same invocation might succeed on a second attempt. A storyboard is validated before any generation, so a 2 never leaves half-finished work or spend behind.

keryx reel build --workspace launch || case $? in
  2) echo "storyboard needs fixing" ;;
  *) echo "build failed — worth a retry" ;;
esac

Setting up and checking the install¶

These come from the tool framework rather than from Keryx itself, and none of them touch a reel. They have no page of their own — --help covers them — but the first two matter enough to know about.

What the MCP surface tells an assistant about cost¶

keryx mcp exposes most commands as tools. Seven of them spend real money — cover, portrait, cards gen, voice gen, music gen, storyboard draft and reel make — and each one says so in its own description, which is the text an MCP client reads before it decides to call anything. The description names the billing axis, points at --dry-run, and asks the assistant to get your agreement before spending on your behalf.

That disclosure is the confirm. MCP has no interactive prompt: a tool runs as a subprocess with no stdin, so reel make's over-cap question cannot be answered there and such a run is refused rather than asked about. Telling the assistant what a tool costs, and letting it ask you, is the form the protocol actually supports.

The five publishing and credential commands — publish, approve, auth, auth refresh and studio — are not exposed as tools at all. That exclusion is built into the binary and has no runtime switch.

Reel commands¶