To DuckComfy Globals

A generation pipeline is six things: model, CLIP, VAE, positive conditioning, negative conditioning, and sampler settings. To DuckComfy Globals stuffs all six into one object that travels down a single wire. It's the "context bus" pattern - the same idea behind rgthree's Context nodes and Efficiency Nodes' pipes - and its whole reason to exist is that a graph with half a dozen fat cables running from your loader to your sampler is a graph that's hard to read and easy to break.

The mechanism is a bundle-and-pass. The node takes model, clip, vae, positive, negative, and a ksampler_settings pipe, glues them into a 6-tuple, and hands it out as one BASIC_PIPE called globals. Its sibling From DuckComfy Globals sits at the far end and unpacks the whole thing back into individual sockets for your KSampler, so the only thing crossing the middle of your workflow is a single clean wire. That's the entire trade: fewer cables, and in exchange you accept the context-bundle failure mode every pipe system has - if a node on the bus passes stale values, you can't see it in the wire, because it's all hidden inside one blob.

The inputs

• model (MODEL), clip (CLIP), vae (VAE) - the loaded model stack, normally straight from a checkpoint loader.
• positive and negative (CONDITIONING) - your encoded prompts.
• ksampler_settings (BASIC_PIPE) - the seed/sampler/scheduler/steps/cfg bundle from the pack's To KSampler Settings node.

All six are required. There's no optional lane, so the bundle is only ever complete - which is honestly the right call for a bundle node, because a half-built globals is a debugging nightmare.

The output

• globals (BASIC_PIPE) - the whole pipeline in one object, ready for From DuckComfy Globals.

How to install it

It ships in the duckcomfy personal nodes pack, a utility grab-bag that author duckcomfy re-implements from other sources to stay dependency-light. ComfyUI Manager, search "duckcomfy personal nodes"; or:

cd ComfyUI/custom_nodes
git clone https://github.com/duckcomfy/duckcomfy_personal_nodes

Restart and look in the "duckcomfy" category. No models to download, no Python dependencies - the pack's pyproject.toml declares none.

Gotchas

The BASIC_PIPE type name comes from Efficiency Nodes, and the pack goes out of its way to keep its scheduler lists compatible with that ecosystem - but the tuple layout here is DuckComfy's own, so don't expect to swap globals with an Efficiency pipe node and have it just work. If you already run Efficiency or rgthree's Context, you may not need this node at all; it earns its place if you're already in the DuckComfy loop, or if you want one self-contained bundle you can copy between workflows without adopting a whole other pack. And keep the From node on the same canvas - a globals wire with nothing unpacking it is just a cable to nowhere.