PackAny (Yogurt Nodes)

Every ComfyUI power user eventually hits the wall: your workflow has grown so many parallel wires - a seed here, a strength there, a model name, a scale - that the graph looks like spaghetti and half the connections are just transport. YogurtPackAny is the "put everything in one box" node: up to 32 inputs, all * (any type), and a single pack output that carries them as one value.

• item1 through item32 - all optional, all any-typed.
• pack out - a PACK_TUPLE holding everything in order.

That's the whole node. No settings, no configuration. The trick is what you do with the other end: the same pack ships YogurtUnpackAny, which splits a PACK_TUPLE back into individual values. Pack here, unpack there, and a whole fan of wires collapses into two.

Why you'd bother

Two reasons, and they're both about readability.

First, cleanup. Take a cluster of "config values" that feed a group of nodes, pack them at the source, unpack them right before the consumer. The middle of the graph loses a dozen crossing wires. This is the same organizing impulse that made rgthree's Context nodes a staple - fewer visual wires means you can actually see the pipeline.

Second, modularity. When you package a sub-workflow, a single PACK_TUPLE in and out is a clean interface - the guts can change without re-wiring everything around it.

The one thing to internalize: order matters. PackAny preserves the order you connect, and UnpackAny hands values back in that same order. It's a tuple, not a dict - there are no names. Get the order wrong on one end and the wrong value lands in the wrong input, which is a fun bug to chase.

Install

Part of ComfyUI-YogurtNodes, a single-maintainer grab-bag that flies well under the community radar - no reddit threads, no drama, just a quiet collection of 152 practical nodes. ComfyUI Manager → search ComfyUI-YogurtNodes → install, or:

cd ComfyUI/custom_nodes
git clone https://github.com/yogurt7771/ComfyUI-YogurtNodes.git
cd ComfyUI-YogurtNodes
pip install -r requirements.txt

Restart ComfyUI; find it under "Yogurt Nodes" (display name "PackAny (Yogurt Nodes)").

If you're deciding between this and the same pack's dict nodes (YogurtToDict, YogurtDictMerge, etc.): reach for PackAny when the order is fixed and you just need transport, reach for a dict when you want named access to the fields on the far side. Named is safer; packed is simpler.