MiniMax H3 Chapter Recovery Load

The MiniMax H3 Context Loop pack renders long multi-scene videos by checkpointing every scene, which is great for resilience and a pain for recovery: reloading one chapter shouldn't mean loading and extending the entire run. MiniMax H3 Chapter Recovery Load is the answer to that. It's the rescue sibling of Chapter Delivery - that node seals a chapter into an immutable snapshot, this one reopens it, on its own, leaving everything else in the run untouched.

You reach for it when a chapter was already delivered and you need that exact final again - a client re-request, an old version to compare against a retake, or a chapter you want to run through an upscaler without re-rendering anything. It doesn't resample video; it reads back the saved manifest and feeds it to whatever finishing node you connect.

How it works

Chapters are saved as immutable snapshot manifests under output/h3_chains/<run_name>/chapters/<number>_<chapter_id>/. Give this node the run name and chapter number, and it loads the newest saved snapshot for that chapter; paste a complete 32-character snapshot id and it restores a specific older delivery instead. It's non-destructive - no media is moved, deleted or re-queued - and it returns a verified manifest you can hand to Assemble, Export PNG Sequence + Audio, or an upscale adapter.

The three inputs are all you need to set:

• run_name - the exact run that holds the chapter. It must match what you used when generating; case and spelling count.
• chapter_number - which chapter (1 to 128).
• chapter_manifest_id - leave blank for the newest snapshot; paste a full 32-character id to recover an older final.

Outputs: chapter_manifest (H3_CHAIN_MANIFEST, the one that plugs into any finishing node), plus manifest_json for eyeballing what you recovered, chapter_manifest_path for where the snapshot lives, and a status string with the recovered range and snapshot id.

The catch to know about

A recovery manifest is references, not a copy of all the media. The node verifies the snapshot's checkpoint lineage, but the actual scene checkpoints and project assets still need to exist on disk - the pack's Checkpoint Manager protects files referenced by sealed snapshots from deletion, so if you let it manage cleanup you're fine; if you hand-delete run folders, you can break a sealed chapter even though its manifest loads cleanly.

Install

With the pack via ComfyUI Manager (search "MiniMax H3 Context Loop"), or:

git clone https://github.com/seitanism/ComfyUI-H3-Motion-Context-MultiRef.git
git clone https://github.com/ethanfel/ComfyUI-MiniMaxH3-Contex-Loop.git

then restart ComfyUI. This is a 0.6.1 addition, so if the node doesn't exist in your palette, update the pack first.

Troubleshooting notes: if the load fails, first confirm the chapter was actually sealed with Chapter Delivery - a generated chapter that was never delivered has no immutable snapshot to load, and this node won't invent one. Blank id loads newest, which is the footgun in reverse: it will happily grab last week's version if you forgot you re-delivered. When the exact final matters, read the chapter_manifest_id off the Delivery node's status and paste it.