MiniMax H3 Contex Loop Load Manifest

MiniMax H3 Contex Loop Load Manifest is the "I closed ComfyUI two weeks ago and now I want my movie back" node. The chain's rendering loop produces a manifest only when the final scene is accepted - but everything it needs to reconstruct that manifest lives on disk as checkpoints. This node validates the longest contiguous saved scene prefix and rebuilds a completed or partial manifest without rendering a single frame. Connect its output to Assemble and you're done.

That's a bigger deal than it sounds. The whole pack's philosophy is "scene plans that survive the render" - accepted scenes are persisted as checkpoints precisely so a production can outlive a session, a reboot, or a GPU change. Manifest Load is the recovery side of that bargain: it's the read-back path that makes the persistence useful.

The inputs

• plan - the same validated H3 Chain Plan you rendered with. Plan and generation fingerprints are checked against every saved scene. You can't hand it a fresh Plan with different prompts and expect it to load - that mismatch is the safety rail that stops you assembling scenes that were never meant to go together.
• source_audio (optional) - the original full source track when the Plan selects final source audio or enables Source reference. Its fingerprint must match the saved checkpoints. This is the legacy route.
• source_timeline (optional) - the primary 0.5 recovery route. Reconnect the same Source Timeline, or leave it blank when the path-backed descriptor is already stored on the managed Plan.
• external_context (optional) - reconnect the same Existing Video Context used for scene 1. Its tail fingerprint restores the correct resume contract, and its persisted prelude stays available to Assemble.

Note the design: none of the optional inputs are needed when your Plan and run are fully self-describing (0.5 makes them so). They exist for the legacy cases and for media that wasn't persisted.

The outputs

• manifest - the verified completed or partial manifest, reconstructed from the longest contiguous saved scene prefix. Connect to H3 Chain Assemble.
• manifest_json - human-readable JSON of the reconstructed manifest.
• status - a STRING with the number of verified scenes and the checkpoint directory used. Read it to confirm you got what you think you got.

The "longest contiguous prefix" bit is worth calling out: if scenes 1–3 are saved but scene 4 isn't, you get a 3-scene manifest, and Assemble will happily join those three. That's the partial-assembly use case - approve-and-stop, or a crash mid-run, still leaves you able to cut what completed.

Installing it

Part of ComfyUI-MiniMaxH3-Contex-Loop (ComfyUI Manager: "MiniMax H3 Contex Loop"), or:

cd ComfyUI/custom_nodes && git clone https://github.com/ethanfel/ComfyUI-MiniMaxH3-Contex-Loop.git

Restart ComfyUI. Standing requirements: H3 weights, current ComfyUI with native Add Guide (PR #15439), and ffmpeg (or PyAV) for the assembly step that follows.

Common issues

The classic failure is fingerprint mismatch: you changed the Plan (a prompt, a seed, a reference) since rendering, and Manifest Load refuses. That's correct behavior - the checkpoints were generated under the old contract. Either restore the original Plan or treat this as a different run. And if you get fewer scenes than you expected, check status: it tells you exactly how many scenes verified and where the prefix stopped, which usually points at a deleted or corrupted checkpoint.