Hanzo Studio's workflow backend: every creation — an image, a poster, a document, a deck, a type system, a 3D model, an ad, a film, a voice, a song — is a run of a graph of steps that the person who started it owns.
Every command takes --json for the raw response and --help for its own flags. Sign in once with hanzo auth login; the commands below use that session, and the org they act in is the one it carries.
Command
What it does
hanzo studio chat
One chat turn that plans and launches runs, streamed
hanzo studio estimate
Prices a run without starting it: the estimate POST /v1/studio/runs would reserve, step by step.
hanzo studio gpus
Lists the GPUs your org has linked with hanzo link that can take a studio.render step, each with whether it is free now.
Cancels one of your runs: a step in flight is told to stop, nothing new starts, and the reservation settles to what finished steps cost.
hanzo studio runs create
Starts a run: name exactly one of template, flow or graph, with the input its inputs schema asks for.
hanzo studio runs events <id>
Stream a run's progress as Server-Sent Events
hanzo studio runs get <id>
Reads one run: its graph, its input, every step's state, the assets it made and what it cost.
hanzo studio runs list
Lists the runs you may read — your own and those your org shares — newest first.
hanzo studio runs retry <id>
Resumes one of your runs that failed or was cancelled: the steps that did not succeed run again in the same run, and the steps that did keep their outputs and are neither run nor charged again.
hanzo studio runs update <id>
Renames or shares one of your runs.
hanzo studio runs versions <id>
Lists every version of a creation you may read — the runs in this run's lineage — oldest (version 1) first.