MiniMax H3 Creator Resume Plan / 下一候选与继续位置 (Advanced/T8)

The classic mid-production question: "which shot am I on, which variant was I trying, and what do I do next?" When a shoot spans days and dozens of seed variants, the answer lives somewhere between your notes app and your memory, and both lie. MiniMaxH3CreatorResumePlanT8Advanced is the node that answers it from the actual source of truth - your immutable Creator Workspace and, optionally, a receipt ledger of what already ran.

The description is a model of restraint: "Finds the next explicit render, review or retry from an immutable Creator Workspace and optional receipt ledger. It never queues, cancels or deletes." Everything this node does is read-only. It doesn't push work into the queue, doesn't cancel a stuck job, doesn't touch a file. It computes a plan and hands it to you (or to a gate that acts on it). That's what makes it safe to leave in a production graph: worst case it tells you the wrong thing; it can't do the wrong thing.

How it works

Feed it a workspace (custom H3_T8_CREATOR_WORKSPACE) and, optionally, a ledger (H3_T8_CREATOR_RUN_LEDGER) of explicit outcomes - completed, accepted, rejected, cancelled, failed. The node walks the plan and finds the next slot that still needs a render, a review, or a retry. Because the workspace is immutable, the answer is deterministic: same workspace + same ledger = same resume plan, every time. That reproducibility is the whole point - "resume" in a long shoot should be a calculation, not a vibe.

What comes out

• resume_plan (custom H3_T8_CREATOR_RESUME_PLAN) - the structured plan object for downstream nodes.
• action (STRING) - what the plan wants next: render, review, retry (mirroring the pack's run-receipt vocabulary), or done.
• run_position, variant_index, attempt_number - the exact coordinates of the next slot, so a seed can be recomputed deterministically.
• summary and report_json - the human-readable version.

The natural downstream is the Creator Run Receipt node: each time a candidate completes, record its outcome into the ledger, and the Resume Plan recomputes. That loop - receipt writes, resume plan reads - is the pack's answer to checkpointing a multi-day shoot without trusting anyone's memory.

The honest limits

It finds the next explicit slot. It can't infer that a shot you never marked as done is secretly finished, and it won't second-guess a ledger that contradicts the workspace - garbage ledger, garbage plan. And it's experimental, so the author's validation stops at mechanical correctness on real three-shot plans; the resume quality of H3 output is a separate, unclaimed question. Use it for logistics, not for taste.

Install

Standard pack install:

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

Restart ComfyUI. It's in T8/MiniMax H3/Studio/Experimental next to the other Creator nodes, needs no extra dependencies and no models - pure plan/ledger arithmetic. The reference is 2026-08-23_H3_Creator_Run_Receipt_Resume_Advanced.json in the 11-studio-production examples, which shows the receipt + resume loop wired end to end. Set up the loop once on a small plan, and the next time you open a project three days later, the node will tell you exactly where you left off.