# Command-Line Flags
URL: /cli

Every command-line flag an OpenHTF test script accepts — -v verbosity, --config-file, --config-value, --config-help — and the dashboard_server flags, with how to combine them with your own argparse.

An OpenHTF test is a plain Python script, but the framework registers a few flags that any script accepts once `test.configure()` or `test.execute()` has run.

Console log verbosity. No flag: framework logs only. `-v`: `info` and above from phases and plugs. `-vv`: `debug` and above. See Logger.

Load configuration from a YAML or JSON file. Equivalent to `CONF.load_from_file()`. Values from the file override declared defaults.

Set one configuration key. Repeatable. Overrides both defaults and the file. The value is always a string — cast in code if you need an int.

Print every declared configuration key with its description and default, then exit. Run it on your own test to document its knobs.

Standard argparse help, including the flags above.

Flags are parsed with `parse_known_args()`, so unknown flags are left alone for your own parser.

OpenHTF exposes its parsers as `ARG_PARSER` objects you can pass as parents:

The multi-station dashboard is a separate entry point:

OpenHTF itself reads none. TofuPilot's `upload()` callback reads `TOFUPILOT_API_KEY` (see Manufacturing Test Analytics). A common pattern is to gate optional phases on an environment variable with `run_if` — see Run if.

<Card title="Configuration" href="/configuration" description="Declaring the keys these flags set." />

<Card title="Logger" href="/logger" description="What -v and -vv print." />

<Card title="Production deployment" href="/guides/production-deployment" description="Per-station config files and launch scripts." />