MiniMax H3 Patch Priority

On a current ComfyUI, this node does almost nothing - and that's the entire point. It's a conditioning pass-through that exists to run at the right moment in the graph: wired directly between your Ref2VA/I2V node and Contex Loop Context, it guarantees it executes before continuation guides get added. On newer ComfyUI builds, where core owns the native H3 guide path, that's all it has to do. The node's real work only happens on the legacy fallback, and it's the kind of work you hope you never need.

What it does

The input and output are the same conditioning value, untouched. You also get a status string that tells you which of two worlds you're in:

• Core-owned native guide - updated ComfyUI handles MiniMax H3's Add Guide natively (merged PR #15439), so no patch is installed and the conditioning flows straight through. This is the good case, and it's the default on maintained ComfyUI.
• Legacy fallback - on older builds, the pack's vendored runtime patch may need to own a spot in the graph. When that happens, this node may replace only an older compatible copy of H3 Motion Context's wrapper (the pack deliberately shares a patch-ownership ABI with NikoDemon80's upstream pack so both can be installed without double-wrapping). It retains recognized H3-Multishot/SolAttn behavior, refuses unknown wrappers, and the ownership is process-global after execution.

The practical read: leave this node in your graph where the workflow template puts it, and let it do its quiet thing. If status says core-owned, great - it's a free check that your ComfyUI is current. If it says a legacy patch claimed ownership, that's a signal your ComfyUI is old enough that you should update, because you're running on fallback behavior.

Install and gotchas

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

Restart, or install via ComfyUI Manager under "MiniMax H3 Contex Loop". No pip dependencies. Models aren't bundled - see the MiniMax H3 Community License for the territory restriction on local weights.

The one real gotcha is upstream: if you see the one-time warning about the legacy fallback, treat it as "update ComfyUI," not as something this node will fix forever. And don't reroute the conditioning around it to "save a node" - the pass-through position is what orders execution, and skipping it can let guides land before the node that needs to see the raw conditioning.