🌀 BV Pipe [Deprecated]

BV Pipe is the carrier node in the BV Pipe system: it takes the slot layout defined by BV Pipe Config, shows you those slots as inputs and outputs, passes every value through, and lets you override individual slots when you need to. It's the cable; Pipe Config is the label sheet; your model, clip, vae, seed, prompt values are the current flowing through it.

If you've built a serious ComfyUI workflow, you know the pain this exists to solve. The ecosystem docs describe the whole Quality-of-Life node category - rgthree Context nodes, Efficiency Nodes - as a response to graphs too wide to fit on screen. A pipe collapses five or ten wires into one. That's the deal here: reorganize your graph by dragging one connection, and every value travels with it.

How it works

The mechanism is refreshingly simple, and the source is easy to read if you want to verify it. The pipe input is a BV_PIPE object carrying two things: the slot config (names) and a list of upstream values (items). The node then exposes up to 100 optional inputs named v_001 through v_100, each typed as ANY, meaning it accepts anything - models, latents, ints, whatever.

Resolution order per slot: if you explicitly connected that v_0xx input, your value wins. Otherwise the value from the upstream pipe passes through untouched. Outputs out_001…out_100 mirror the final resolved values in the same order, and the pipe output carries the whole bundle forward so the next BV Pipe in a chain keeps working.

So you get both behaviors the README advertises in one node:

• Passthrough - leave every slot unconnected and it's a straight relay, useful for routing a bundle through a subgraph.
• Override - connect one slot on a later pipe to swap, say, the seed, while everything else still flows from upstream. That's the "slot override" case in the README's screenshots.

The inputs that matter

• pipe - required BV_PIPE input from a BV Pipe Config. Without it there are no names and the node has nothing to route.
• v_001…v_100 - optional ANY inputs. You only see the ones defined by your config's names, and only the ones you wire. These are the overrides.

Outputs: pipe plus out_001…out_100, mirroring the resolved values. If you're following the README quick start with five names, you'll see exactly five outputs.

Install & gotchas

Install is shared across the pack - ComfyUI Manager → BV Node Pack, or clone https://github.com/BlackVortexAI/bv_nodepack into custom_nodes, then restart and Ctrl + F5 hard-refresh. The hard refresh is not optional for this node: the dynamic slot rendering is a JavaScript extension, and a cached frontend will render it as an inert box. No model downloads, no requirements.txt - nothing heavy to babysit.

Two gotchas. First, the internal slot IDs are stable (v_001…), so if you reorder names in Pipe Config, values stay attached to their old internal slot - the label moves, the value doesn't. Second, an honest heads-up: the current source marks BV Pipe (and Pipe Config) as deprecated in favor of the pack's newer BV Smart Pipe and BV Smart Pipe Merge, which are JSON-schema driven and handle merging and routing more robustly. For a quick bundle-and-override pipe this node is still perfectly serviceable. For anything you expect to grow and hand to other people, start with the Smart Pipe instead.