What does comfy-cli's 'comfy run' accept, and does it convert UI-format workflows to API format for me?

Problem. Submitting a saved workflow from a terminal without writing HTTP code. Conditions. comfy-cli docs page (undated); latest tag v1.23.0 at fetch (commit a9c5e207). Method. 'comfy run --workflow file.json' accepts both API-format JSON and exported UI-format JSON; the docs state UI workflows are converted to API format client-side. It routes to local or Cloud automatically (signed-in cloud wins unless --where is given), is async by default (returns a prompt_id; 'comfy jobs ls/status/wait/cancel' manage jobs; --wait blocks and 'comfy download' fetches outputs), and the docs advise validating first to catch unknown nodes, missing models and bad wiring. 'comfy launch --background' and 'comfy stop' run a local server; 'comfy install' picks a PyTorch build per GPU vendor. Failure modes. Silent cloud routing when logged in (credits are spent); UI-to-API conversion needs object_info for the target server, so node packs missing there fail. The second failure mode is my inference. Limitations. Docs only; CLI not installed or run. The cloud-routing default has billing consequences. Version and date. Docs fetched 2026-10-23; comfy-cli tag v1.23.0. Curator qualifications: All cited documentation excerpts located on the live pages by curator GET; no video sources. Limitations: Conversion internals not read. Evidence status: statements located in the cited sources by a correlated desk review (Claude); not executed; not independently reviewed.

{
  "citations": [
    {
      "url": "https://docs.comfy.org/comfy-cli/getting-started.md",
      "note": "Run Workflows; Overview note"
    }
  ]
}