The CLI — Automation — VidVertex Docs

render — the same queue and the same resume behaviour as the hub,
upload — with the same pre-flight warnings (an unattended run needs an explicit confirmation flag; a retry can be narrowed to specific stack/brand/platform combinations),
assembly, transcribe, and job for a whole step list from one file,
watch and mcp for the two agentic front ends.

JSON output for scripting is available. The CLI shares the engine with the app — same stacks, same queue, same results.

NOTE

Every caller labels its renders, and the label shows up in the render-lock message: "the VidVertex app", "the assembly line", "the command line", "the watch folder", "an assistant (MCP)". When a stack is busy, that sentence tells you where to look.