placeholder tuple

Here's the honest version up front: Placeholder Tuple does not produce a real SDXL tuple. The node declares an SDXL_TUPLE output, and its source literally builds a string that looks like a tuple's repr and splits it into chunks. If you wire that into something that actually unpacks the tuple, it will break. The author is upfront about this - the README says it's for "times when you need to fill a Tuple but aren't going to actually use it."

So why does it exist? Modular workflow development. When you're building a reusable template, an empty tuple socket is a magnet for trouble: ComfyUI and some custom node packs try to "fix" open required inputs by auto-wiring whatever matching output is around, and other times an empty socket just breaks the load. This node fills that socket so the workflow stays structurally sound while you're still wiring it - the same job the pack's passers do, but for a type the pack doesn't otherwise generate.

When it's actually the right tool

The scenario the author describes: you're shipping a template workflow where the tuple slot gets filled at runtime by an invisible-wiring system (the Use Everywhere / Anything Everywhere family) or by a real loader when the user supplies it. Until then, Placeholder Tuple plugs the hole so the graph loads, saves, and shares without erroring. Think of it as a placeholder object in code - a stub with the right type signature and no real behavior.

That means the rule is simple: never wire the output anywhere it will actually be consumed. If something downstream reads the tuple's contents, you get nonsense. If it just needs the slot satisfied, this is exactly the node.

Inputs and outputs

• No inputs at all - both required and optional sets are empty. You just drop it in and it sits there being a placeholder.
• Output: sdxl tuple (typed SDXL_TUPLE, but effectively garbage if inspected).

Installing it

Same pack, same steps:

cd ComfyUI/custom_nodes
git clone https://github.com/aegis72/aegisflow_utility_nodes

Restart ComfyUI, or install "AegisFlow Utility Nodes" via ComfyUI Manager. No models, no dependencies.

Where people get burned

People wire it into a real consumer and get a confusing error about tuple contents. Don't. If you need an actual SDXL tuple, use a real SDXL loader; if you need a socket filled while a sender or user supplies the real thing at runtime, this is your node. Also worth knowing: this is the pack's only node in the AegisFlow/placeholders category, and it shows how much of this pack is really about keeping large modular graphs alive while they're being built.