Skip to main content
Use loomloom <command> --help as the syntax source of truth for your installed version.

​
Global options

Global flags apply across command groups. Inspect the installed CLI for the complete current set:
Use --output json when another command or program consumes the response, and preserve returned IDs exactly. Default text output is intended for people.

​
Official programmatic input

The CLI separates the official-template JSON/JSONL flow so the estimate can be reviewed before execution:
run execute optionally accepts --callback-url <https-url>. Use --client-request-id for safe retries; --idempotency-key remains only as a deprecated compatibility alias. The former combined run submit command is legacy and hidden, so new integrations must use the staged flow.

​
Built-in TemplateSpec documentation

Choose a bundled topic and language explicitly when needed:
Topics include spec, authoring, examples, conversation, metadata, inputs, steps, bindings, and execution-units; use all for the complete set or omit the topic to print the index. The default language is English. For Excel input, continue to use template validate-file → template precheck-file → confirm → template submit-file.

​
Safety boundary

Discovery, downloads, uploads, validation, precheck, and quote are preparation steps. Commands that create a hosted run or change remote resources require explicit confirmation after the user has seen the current action and, for a run, its fee estimate. See the complete loomloom CLI developer reference.