ComfyUI-H3-Continuum builds longer MiniMax H3 sequences from chunks while retaining video and audio latent context. Its practical value includes saved-run recovery, selective regeneration, per-chunk references, and control over the memory and temporary files needed to assemble the result. These are project-workflow features, not a new H3 checkpoint.
This guide reviews the author's README and 3.9.4 release on October 14, 2026. Instructions below come from documentation; H3Vid has not installed this package or reproduced its GPU checks. The current package is 3.9.4, while the working node names remain V3.9.
Choose the right kind of extension
The online MiniMax H3 Extender starts from an uploaded playable video. Continuum instead owns chunk sampling, paired audiovisual latent state, and assembly inside ComfyUI. Exporting an MP4 from a local workflow does not preserve everything needed to resume its latent project.
The H3 Project Suite is another local pack with its own approval and project organization. Its settings and saved projects should not be assumed interchangeable with Continuum Runs and Takes. Choose the pack whose maintained graph and recovery model fit your project, rather than mixing similarly named nodes from separate tutorials.
Installation and version selection
Use the author's fixed-version release or ComfyUI Manager entry and open the matching template. A workflow ZIP contains node wiring; it is not the custom-node package installer. Install the nodes, their required models, and any external template dependencies separately.
The template gallery includes both V3.9 and retained V3.8X2 graphs. Opening an old graph does not convert its reference sockets or saved state to V3.9. Preserve the old workflow and start new V3.9 work from the dedicated graph. After updating the package, restart the backend and hard-refresh the browser so Python and JavaScript belong to the same installation.
The 3.9.4 release repairs Registry packaging and version metadata. It includes a previously omitted restoration guide and checks archive contents and hashes. It does not change sampling, twelve public node identities, official workflows, or saved Runs/Takes. Registry publication, service scanning, and successful installation through Manager are separate states; the author's release notes do not claim a new GPU generation test for this packaging repair.
Assign references before queueing
V3.9 uses a Reference Images helper with nine fixed image slots and a chunk-assignment table. Connect its reference output to the V3.9 Sampler. In the supplied template, several image loaders begin bypassed and the per-chunk assignments are unchecked. A connected image therefore does not automatically become an active reference.
- Choose actual image files and enable their loaders.
- Tick the chunks that should use each image, or deliberately select All chunks.
- Refer to fixed slots with
@R1through@R9in the sequence prompt. - Confirm the output-size mode and any separate First Image or Last Image.
Slot numbers remain stable when intermediate slots are empty. The backend maps active references to actual picture numbers for each physical group. A character may remain visible after its reference is no longer assigned because prior video context still carries that character; removing a reference is not an instruction to remove the person.
The official graph's First Image and size defaults also matter. For a references-only trial, explicitly disable First and Last Image and choose the intended manual dimensions. Reference Image Size changes conditioning after source loading, so large source files can still consume host RAM before that control applies.
Resume and regenerate a later chunk
Enable Save + Auto Resume before the first generation. Use a stable Run Name and Base Seed. A run made with storage off cannot later recover latent chunks that were never saved.
For a two-chunk sequence, the author's documented pattern is to complete both chunks, retain the generation settings, and set Regenerate From to Chunk 2. The compatible first chunk is reused as continuation context, while a new second chunk is sampled. The assembled output is decoded again and seam processing is reevaluated; prefix sampling reuse does not mean the complete job performs no work.
Keep the model, LoRA, resolution, sampler, sigma schedule, references, prompt plan, and continuation settings stable when reuse is intended. Changing the generation contract may create a new revision. Plan different chunk prompts before the initial run rather than expecting a changed prompt plan to reuse every old prefix.
Variation Nonce zero requests automatic new variations after completed regenerations and resumes a compatible interrupted variation. Reusing the same positive nonce does not request a new variation. FL2VA Terminal Merge is an exception to simple chunk independence: its final two logical chunks form one physical sampling group and regenerate together.
Move temporary storage without moving your project
The October 13 storage update adds Settings → H3Continuum → Storage → Manage temporary storage. The selected folder is on the ComfyUI server, not necessarily the browser's computer. Validate and save it only when running and pending queues are empty.
This location controls scratch writes from Finalize and Decode Cache Helper. Saved Runs/Takes and finished videos retain their existing locations. New temporary files use the selected folder; existing outputs remain usable at their old location. A missing selected drive does not silently redirect the job to the original SSD.
Moving to another folder on the same physical drive does not reduce that drive's writes. Disk-backed assembly lowers anonymous host-memory pressure but can add I/O cost. It does not reduce sampler VRAM, and downstream nodes may allocate a full RAM copy. Turning Decode Cache off also does not turn off Finalize's disk buffer.
A useful first check
Start with two short chunks, small references, and the maintained template. Confirm the selected files and assignments, generate once, then regenerate the second chunk while checking the reuse report. Test recovery before committing to a long film. These are proposed validation steps, not results obtained by this site.
If storage status returns HTTP 404 after updating, the README identifies an old backend still holding the port as a possible cause. Refreshing status does not restart that backend. Check the startup log and loaded version before changing the workflow. Keep original projects and outputs while troubleshooting: continuity controls help manage generation, but they do not establish unlimited length, zero seams, or invariant identity across every scene.