🌀 BV Smart Pipe

Every ComfyUI power user hits the wall where a workflow needs to carry model, clip, vae, positive, negative, latent, seed, and a handful of misc values down a chain - and the graph turns into a spaghetti of reroutes. Pipe nodes fix that by bundling values onto one wire, but most pipe systems are rigid: every node in the chain exposes the same fixed port list, whether or not it's relevant at that point. BV Smart Pipe is the version that grows.

The idea is incremental slot inheritance. Instead of one global pipe contract stamped on every node, each Smart Pipe node inherits the slots of the node it's connected to and can add its own. A loader pipe carries model, clip, vae. A downstream prompt pipe carries those plus positive and negative. The sampling pipe carries all of that plus latent and seed. You only see the ports that make sense where you are, and every slot keeps a stable logical identity throughout the chain.

How it works

Configure a node through Configure Smart Pipe (right-click / node menu): define its schema - which slots exist and their types - and its route. The node then exposes exactly those slots as its inputs and outputs. Two JSON fields drive it, bv_smart_pipe_schema_json and bv_smart_pipe_route_json, but you should be using the config UI, not editing those by hand.

Three behaviors make it worth learning over a plain pipe:

• Stable slot IDs beat names. Because every slot has a fixed logical identity, downstream connections keep pointing at the right value even if a label changes upstream or a slot is temporarily missing. That's the pack's core philosophy - "stable IDs are authoritative; names are presentation" - applied to pipes.
• Branches inherit independently. Each branch of a wireless or wired tree inherits only its own upstream slots and can grow on its own, then rejoin via BV Smart Pipe Merge in explicit order.
• Failures fail closed. Missing sources and cycles don't silently shift your connections around; they error visibly.

There's also wireless routing - the pack's take on "use everywhere" style broadcasting, no visible wires needed. Here's the honest caveat from the README: wireless routing across Subgraph boundaries depends on prompt materialization because ComfyUI doesn't yet expose an official pre-prompt extension hook. If your workflow is compatibility-critical, keep physical pipe links. The pack says it straight: "Keep physical pipe links in compatibility-critical workflows." That's the one real trap with this system - wireless is convenient until an upstream ComfyUI update changes prompt lifecycle behavior, and then it's a mystery.

What's in the schema

The brief's info_schema shows the mechanics: optional inputs pipe and v_001 through v_100 (any type), outputs pipe plus out_001 through out_100. You don't wire 100 ports - the node presents only the slots your schema declares. The * types mean any value can ride along, so it's less a rigid typed bus and more a "whatever you need" courier.

Install

Search BV Node Pack in ComfyUI Manager, or:

cd ComfyUI/custom_nodes
git clone https://github.com/BlackVortexAI/bv_nodepack.git

Restart, hard-refresh with Ctrl + F5. No pip requirements, no models.

The honest take

Smart Pipe is a real step past the fixed-pipe packs it was inspired by (the README credits motorway-style pipes and Use Everywhere as ancestors), but it's also the most opinionated node in the pack. If your workflow is simple, a pipe is overkill - use one only when you're genuinely fighting reroute spaghetti or want clean Subgraph interfaces. When you do, the incremental inheritance is the feature that sells it. And when the config UI feels fiddly, remember the legacy BV Pipe and BV Pipe Config nodes still exist for old workflows - new work should use Smart Pipe.