Scripting & agents
The same predictable flow that guides a human drives cleanly from scripts, CI, and AI agents. Any selection flag — --license, --set, --headers, --get-tokens, or a --save-* flag — switches off the prompts and runs as a single command, and the standalone modes (--verify, --apply-config, --remove-headers, --force-header) never prompt at all. Which flags require which, which run on their own, and which win when several are combined is laid out in How flags combine.
Exit codes are the contract
Every run signals its outcome through its exit code, so a script or agent always knows what happened without parsing output:
- A successful generation, a clean
--verify, or a healed run exits0. - A missing required field, an unrecognized identifier, a
--verify --strictrun that found drift, or a standalone mode with nothing to act on exits non-zero — and prints exactly what's wrong. - Saved tokens that don't match the license also exit non-zero, in
--verify(with or without--strict),--apply-config, and--force-header, before anything is checked or written.
Standalone modes take priority
The standalone modes — --remove-headers, --verify, --apply-config, and --force-header — own the whole run and ignore the selection flags. When one rides along with a stray --license or --set, the standalone mode still wins, so an agent can replay a saved config or run a verify without a leftover flag quietly changing the outcome. When several are combined they resolve in a fixed order — --remove-headers first, then --verify, then the single-file --force-header, then --apply-config — spelled out in full under Priority when flags are combined.
Tell your agent to use License Wizard and it will: the flags are explicit, the failures are descriptive, and nothing is written until every required field is present.