⬡ Polyhedron Wan Bridge (WANVIDEOMODEL → MODEL)

The forward Wan Bridge (MODEL → WANVIDEOMODEL) gets all the attention because it's the direction most people need: core-loaded model into kijai's sampler. This is its mirror, and it exists for the workflows where the model starts on the kijai side - loaded by WanVideoModelLoader, with all of kijai's optimizations baked in - and has to travel back to a core node that only accepts a MODEL.

Same idea, flipped: take a WANVIDEOMODEL input, re-label the patcher as a plain MODEL, hand it out. The input tooltip spells out what you're getting for free: all kijai optimisations - fp8, Sage Attention, Block Swap - are preserved, because underneath it's the same ModelPatcher the whole time. The bridge only changes the label the type system sees.

When would you actually want this? The realistic case is a hybrid graph where you want to sample with kijai's optimised path but then route the result through a core-ecosystem node that only takes MODEL - a core sampler alternative, a model patch, an upscaler that expects the plain type. The other case is pure convenience: load once through kijai's loader (which gives you the fp8/SageAttention handling you've already tuned), bridge to MODEL, and feed everything downstream without re-loading or re-applying LoRAs through a second path. Since both types are the same object under the hood, nothing about the model's behaviour changes - which is also the node's one real footgun, below.

Installing it

It ships with the forward bridge in the Polyhedron Suite pack:

cd ComfyUI/custom_nodes
git clone https://github.com/PolyhedronAI/ComfyUI-PolyhedronLoRAStack.git
# restart ComfyUI

Or ComfyUI Manager, search "Polyhedron Suite". No extra dependencies, but it's dead weight without ComfyUI-WanVideoWrapper (kijai) installed, since that's where the WANVIDEOMODEL type comes from.

The one thing to internalize: the bridge is a label swap, not a converter. If you feed it a model that isn't actually Wan under the hood, it will happily hand a mislabeled patcher to whatever's downstream and let that node fail on its own terms. And the usual kijai hygiene applies - if you see the pack warn that a kijai symbol is missing, update WanVideoWrapper; a renamed function means the bridge can't apply its patches and you can get double-loading or LoRA conflicts on the kijai path. When both ecosystems behave, this is one of those nodes that disappears into the graph and you forget it exists. That's the point.