Checkpoint Passthrough + Notes (Arctenox's Essentials)

A loaded checkpoint hands you three wires - MODEL, CLIP, VAE - and in a busy graph they trail off in three directions, crossing everything in between. This node gathers them back into one clean connection point and does literally nothing to them. Zero processing overhead, the source just returns the same objects it received.

How it works

The mechanism is about as simple as a custom node gets. execute takes model, clip, and vae, and returns them unchanged. The only bit of actual behavior: the optional notes field, a multiline string that, when non-empty, gets printed to the ComfyUI console. So it doubles as workflow documentation that you can actually find in the logs.

Inputs: model, clip, vae (all required), plus notes (optional, default empty). Outputs: the same model, clip, vae - nothing added, nothing transformed.

When it's worth it

Two honest use cases:

• Readability. Route your checkpoint through this node and you get a named, labeled point in the graph where "the model starts." If you share workflows or come back to them weeks later, that's real value.
• Notes that survive. Type "SDXL base, no refiner, keep cfg under 6" into notes, and every run that section passes through logs that line to the console. It's a poor man's comment block that actually shows up in output.

That said, it's cosmetic. If your workflows are small or you already use group labels, you won't miss it. It shines in the "large graph" scenario - the kind where org packs like rgthree exist for the same reason. This is the pack's lightweight answer: one node, three wires, a notes box.

Install

With the rest of Arctenox's Essentials, via ComfyUI Manager (search Arctenoxs-Essentials_ComfyUI) or:

cd ComfyUI/custom_nodes/
git clone https://github.com/Arctenox/Arctenoxs-Essentials_ComfyUI

Restart ComfyUI after. No model downloads. It needs nothing beyond torch/numpy (and psutil only if you want the pack's memory monitoring elsewhere). Fair warning from the README: the pack is marked deprecated while the author remasters it into a new pack - the passthrough is the kind of trivial node that may not make the cut, so don't build your identity around it.

Troubleshooting

The only confusion is expecting it to do something. It won't - by design. If a workflow you downloaded references it and ComfyUI says the node is missing, that just means the pack isn't installed, not that the node is broken. And since it returns the same tensors, you can't "damage" a checkpoint by routing it through here; worst case you printed a note to the console you didn't want.