Voyager runs vork on its cloud GPUs.

Render with Vork (https://github.com/voyager-so/vork) on Voyager cloud GPUs.
Needs a paid Voyager workspace (Starter or above). If access is refused, show me the billing link from the error.
1. Install the CLI (if voyager-cloud isn't installed yet):
   macOS / Linux:  curl -fsSL https://voyager.so/cloud/install.sh | sh
   Windows (PowerShell):  irm https://voyager.so/cloud/install.ps1 | iex
2. Sign in: voyager-cloud login (opens my browser). If VOYAGER_API_KEY is set, use it instead. Never ask me to paste a key.
3. Read the guide: voyager-cloud help vork
4. Lease one GPU and wait until it is ready: voyager-cloud lease render --wait --json  (render-lite is cheaper for drafts)
   Keep the machine id. Reuse this one machine for the whole session; don't lease one per render.
5. Once per machine: voyager-cloud exec <machine> -- vork setup   (up to a few minutes with no output; it is not hung)
   Then voyager-cloud exec <machine> -- vork help   for the scene format.
6. Loop: edit the scene locally → voyager-cloud push <machine> scene/ →
   voyager-cloud exec <machine> -- vork render scene/shot.json --profile std/previs --out out/preview.png
   (exec waits and prints the output; a non-zero exit means the render failed) →
   voyager-cloud pull <machine> out/ → look at the image → revise.
   Use std/previs or std/draft while iterating; std/final (or std/path) only for the final render.
   Long renders: voyager-cloud exec --detach <machine> -- vork render … prints a job id;
   then voyager-cloud logs <job> --follow and voyager-cloud wait <job> before pulling.
7. When done: pull the final outputs, then voyager-cloud release <machine>. It bills until it is released or paused
   (idle machines pause by themselves after 15 minutes). Tell me the cost (release prints it).
Using MCP instead? Add https://mcp.voyager.so/mcp/machines to your agent; it has the same steps as tools.