pack_Pack

If you found this node because it's sitting red or orphaned in a workflow you downloaded, here's the short version: pack_Pack is deprecated. Not "old and unfashionable" deprecated - literally filed by the pack's own author under a category folder named Deprecated with a prohibition emoji on either side. In ComfyUI, when a custom node pack marks something this explicitly, it's the author telling you not to build new things around it, usually because a workflow or an internal architecture the node depended on has moved on.

There's not much to the node itself, which fits the story: no required or optional inputs at all, and a single output called PACK of a custom type also named PACK. That's it. Whatever this node was originally meant to do - the schema alone suggests something like "produce an empty container object that other Apt_Preset nodes could then fill in and consume as a bundle" - the pack's changelog and README don't describe it, and the node carries no description of its own. That absence, combined with the deprecated folder, is a stronger signal than any explanation would be: this was part of an earlier design the author has since replaced.

Why this probably happened. ComfyUI-Apt_Preset's whole pitch, laid out in its own README, is that the author rebuilt the pack around a "Loader → Controller → Sampler" framework specifically because earlier, more ad-hoc ways of wiring workflows together were getting dense, inconsistent, and error-prone as the node count grew. A generic PACK type with no defined shape is exactly the kind of loose abstraction that framework was designed to replace with something more structured - the newer loader nodes (sum_load_adv, load_Nanchaku) output a typed RUN_CONTEXT plus an explicit PDATA preset-save mechanism instead, which is a much more legible contract than "here's an opaque PACK object, do something with it."

What to reach for instead. If you're trying to bundle a model, its text encoders, and your sampling settings into one wire the way pack_Pack's name implies, that's what sum_load_adv (for standard checkpoints and UNets, GGUF included) or load_Nanchaku (for Nunchaku-quantized models) are for in the current version of this pack - both output a context you thread through the rest of the Controller/Sampler stack, plus a preset_save you can use to persist your configuration under a name. If you just need to save and recall a specific set of guidance/sampling parameters, pre_guide and the preset system built into those loaders cover that ground too.

Installing the pack. Even though this specific node is deprecated, the rest of Apt_Preset is actively maintained, so if you're here because a workflow needs the pack and you don't have it yet: search "ComfyUI-Apt_Preset" in ComfyUI Manager, or install by hand -

cd ComfyUI/custom_nodes
git clone https://github.com/cardenluo/ComfyUI-Apt_Preset.git

then run install.bat on Windows for dependencies and restart. pack_Pack will still be present after install - deprecated nodes in ComfyUI packs are almost always kept around rather than deleted, specifically so old workflows that still reference them don't break outright when you open them.

Troubleshooting. If pack_Pack shows up red even after a clean install, that's most likely a different node in the same downstream chain that's actually broken, or an IMPORT FAILED on the whole pack from a missing dependency - there's a documented case of exactly that on r/comfyui, unrelated to this specific node, fixed by checking the ComfyUI console log for the real missing package and reinstalling via Manager. If the node loads fine but a workflow using it doesn't behave the way you expect, the honest advice is to rebuild that section using the current loader nodes rather than debugging a path the author has already walked away from.