Shima Model Pass
Keep your model on the wire, not in a tangle
- model
- model
Shima Model Pass is the model-flavored member of the Passer family: MODEL in, MODEL out, no math, no VRAM touched. It's a type-safe passthrough whose only job is to be a stable anchor for a model signal at the edge of a Shima island.
Why would anyone want that? Same reason as the other passers. Shima's islands auto-connect through the Use Everywhere broadcast system, and a bare MODEL socket in the middle of a graph is exactly the kind of thing UE can misroute - a model wire landing in a latent input produces a baffling error that doesn't point at the real cause. A Passer gives UE a clean, typed target it can't confuse. The pack's own docs describe passers as "stable airports at the edge of each Island," and Model Pass is the one you reach for when the thing crossing the boundary is the weights itself.
The implementation is as minimal as it gets: execute returns (model,) unchanged, and the input is optional so an unwired pass just forwards None instead of crashing. That forgiving behavior is deliberate - broadcast targets that get no signal this run shouldn't take the whole graph down.
The interface
- model - optional
MODELinput, echoed to themodeloutput. That's the entire surface area.
Install
cd ComfyUI/custom_nodes
git clone https://github.com/KDB-USJP/shima_wf
then restart, or ComfyUI Manager → search "Shima". No models, no extra pip packages - which makes sense, since the node deliberately doesn't load anything.
Should you bother?
The honest answer is conditional, and it's the same across the whole Passer family. Hand-wired graph, standard ComfyUI: skip it; a reroute does this. Building island workflows that self-connect via UE: it's part of the glue, and keeping a typed MODEL socket at the boundary of your model-loading island prevents a whole class of "why is my sampler getting a tensor" debugging sessions. One thing worth knowing: this is the only model you'll carry this way - the CLIP and VAE have their own single-purpose passers, and if you need several model-related signals together, the pack's MultiPass and MultiPipe nodes bundle them into one wire instead. For a lone model crossing an island edge, Model Pass is the right-sized tool and it stays out of your way.
Inputs (1)
| Name | Type | Default | Description |
|---|---|---|---|
| modelopt | MODEL | — |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| model | MODEL | — |