MiniMax H3 Creator Workspace / 创作运行窗口 (Advanced/T8)

Somewhere in the middle of a long H3 session you stop generating single clips and start managing a little production: a timeline of shots, a handful of seed variants each, only some of which you actually want rendered this pass. That's the problem this node - the head of T8mars' Creator Workspace chain - exists for. It compiles a run window out of your Studio Timeline: which shots to render (run_from → run_to), which variants to keep, what to retain, and a hold-map sidecar. And it does all of that without queueing anything, loading a model, deleting a file, or changing sampler math. It's a planner, not an executor - which is the whole personality of this pack.

Where it sits

The flow is roughly: Studio Timeline → (one Shot Override per shot you want to tweak) → this Workspace node → Workspace Shot Select → the H3 Conditioning/Sampler nodes → Run Receipt → Retention Plan. This node is the gate between "here's the edit plan" and "here's the actual run." If you've used any ComfyUI plumbing, the shape is familiar: a typed custom value (H3_T8_CREATOR_WORKSPACE) flows forward, carrying the whole decision tree as one wire.

Inputs that matter

• timeline - your H3_T8_STUDIO_TIMELINE, straight from the Studio nodes.
• run_from_index / run_to_index - shot range. run_to_index = -1 means "through the end," and that's the default. Want just shots 3–7? Set 3 and 7.
• include_disabled_shots - default false; flip it if you deliberately disabled shots but still want them in the plan.
• edit_plan - optional; feed it the chained output of your Shot Override nodes so your per-shot overrides actually land in the window.

Outputs

workspace (the custom object everything downstream consumes), run_summary, sidecar_json and workspace_json (the hold-map + full plan as text, handy for eyeballing before you commit), and workspace_notes if you want to leave yourself a note in the JSON. Nothing here touches disk.

Installing it

This node ships in the MiniMax H3 Audio T8 pack (200 nodes, one author's H3 lab). ComfyUI Manager → search MiniMax H3 Audio T8, or:

cd ComfyUI/custom_nodes
git clone https://github.com/T8mars/comfyui-minimax-h3-audio-T8

then restart. The pack has no forced pip dependencies (requirements.txt is literally "# No extra packages") and won't auto-download H3 weights - you supply the H3 DiT, Qwen/MiniMax CLIP, video+audio VAE and LoRAs into the usual models/ folders. And yes, the H3 weights themselves carry the MiniMax H3 Community License, which excludes the US, EU, UK and South Korea - check where you live before you pull them.

The gotcha

Because it "never queues or loads a model," this node is pure bookkeeping - nothing visibly happens when you run it. People expect a render and get a JSON. That's correct behavior: it's the Shot Select node downstream that actually hands a prompt + seed to your sampler. Think of the Workspace as the contract, Shot Select as the call to execute it. If your run_summary shows the wrong range, it's almost always run_to_index - double-check the -1 semantics, it's the one value that surprises people.