Skip to main content

CLI

llmclick run runs the stages a config asks for, validate checks a config and prints its experiment key and stage plan without running anything, recipes lists what this installation can build, and serve starts the HTTP API. Paths in a config and environment/.env are read relative to the working directory; LLMCLICK_ENV names another settings file.

llmclick​

usage: llmclick [-h] {run,validate,recipes,serve} ...

CLI: `llmclick run CONFIG`, `llmclick validate CONFIG`, `llmclick recipes`,
`llmclick serve`.

positional arguments:
  {run,validate,recipes,serve}
    run                 Run the stages a YAML config asks for
    validate            Check a config and print its experiment key and stage
                        plan
    recipes             List the recipes, their stages and the keys their
                        registries accept
    serve               Run the API server (the same as `uvicorn
                        core.api.app:app`)

options:
  -h, --help            show this help message and exit

llmclick run​

usage: llmclick run [-h] config

positional arguments:
  config

options:
  -h, --help  show this help message and exit

llmclick validate​

usage: llmclick validate [-h] config

positional arguments:
  config

options:
  -h, --help  show this help message and exit

llmclick recipes​

usage: llmclick recipes [-h]

options:
  -h, --help  show this help message and exit

llmclick serve​

usage: llmclick serve [-h] [--host HOST] [--port PORT]

options:
  -h, --help   show this help message and exit
  --host HOST
  --port PORT