MiniMax H3 Generation Profile

If you've opened a MiniMax H3 Contex Loop workflow, you've seen the part that makes people bounce: a chain_policy input on Plan with a name that sounds like an internal plumbing type - because it is one. This node is the human-readable front end for it. Instead of wrestling with transition presets and audio policy flags, you get two dropdowns with sentences in them, and the node compiles them into the exact same stable Chain Policy object Plan builds on its own.

That last bit matters more than it looks. Contex Loop stores the resolved policy in its checkpoints based on behavior, not graph topology, so a scene you generated through this node and a scene generated from a Plan with its internal defaults stay checkpoint-compatible. That's why the node description is honest about the deprecated Manual Chain Policy: you basically never need it. If a combination of continuity and audio you want isn't in these two dropdowns, the list is short enough that you can just pick the closest pair.

The two inputs that actually matter

Scene continuity - how each new scene connects to the one before it. Your four options:

• Visual continuity (default): carries a short RGB guide from the previous scene's tail, so color and general motion flow across the cut without locking the picture.
• Independent scenes: carries nothing. Each scene starts clean. Right for a montage or title cards where continuity would fight you.
• Hard picture + protected audio: keeps both the picture and the audio at the boundary prefixes exact. Use it when the next scene literally starts from the previous one's last frame.
• Hard picture + smooth audio: picture stays exact while carried audio is gently released instead of abruptly cut.

Audio profile - six choices, and they span two separate questions: does H3 generate the sound, and what ends up in the final MP4. Generate audio (default) keeps H3 sound continuous across scenes. Generate fresh audio per scene starts each scene clean. Lip-sync to source audio protects the exact Source Timeline window during generation and uses that source track in the finished MP4 - this is the one you want for dialogue scenes. Generate audio from source guide lets H3 invent new sound loosely referencing a source track. Use source soundtrack only plays the source track without guiding generation, and No final audio produces a silent assembled MP4.

Both default to the "simple first run" settings the pack's own quick start recommends: Visual continuity plus Generate audio. If you just want to see a scene render, leave them alone.

Outputs and wiring

Two outputs, both useful in different ways. chain_policy is the one you wire - it goes to Plan's chain_policy input, or to Advanced Policy Override if you're pushing on Plan's advanced surface. status is a plain STRING that spells out the resolved continuity and audio behavior, handy for a text preview or for checking what a saved workflow was actually set to.

Installing and the real prerequisites

Install is the same as every node in this pack - no pip step, because the pack ships no requirements.txt:

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

Restart ComfyUI (or search MiniMax H3 Contex Loop in ComfyUI Manager). Two gotchas that bite before you ever see this node's dropdowns: it expects a current ComfyUI build with native Add Guide for MiniMax H3 (ComfyUI PR #15439), and it bundles no models - you still need the MiniMax H3 weights themselves, which run to roughly 42.5 GB. Community reports on day zero said a 3060 can run H3, just slowly, so budget for the card. And if you're in the US, EU, UK or South Korea, check the H3 Community License before you even download the weights - it's geofenced out of those regions.

Where people get burned: this node loads no models and does nothing by itself, so if you forget to wire chain_policy into Plan, your graph just runs on Plan's internal defaults and you might wonder why your settings did nothing. It's a config node - connect it or it's decoration. And "Contex" isn't a typo; it's the pack's intentional spelling. Took me a while to stop "fixing" it too.