Set AutoLink

Here's an honest one: IAMCCS_SetAutoLink does nothing, and that's the whole point. It's a frontend-only virtual node - the backend implementation is literally a noop that returns an empty tuple and is never executed. It's the "Set" half of the pack's AutoLink feature, which converts direct node-to-node links into compact Set/Get pairs to declutter big graphs.

Think of the spaghetti that accumulates when one signal (say, a seed, or a model) fans out to twenty nodes. AutoLink lets you drop a "Set" node at the source and a matching "Get" node wherever it's needed, collapsing twenty visible wires into two compact nodes. IAMCCS_SetAutoLink is the Set; there's a matching IAMCCS_GetAutoLink (and an AutoLinkConverter UI tool that does the actual converting) in the same IAMCCS/AutoLink category.

How it works

In the current shipped source it has no inputs and no outputs at all - it's a placeholder/registration point for the AutoLink frontend feature the pack bundles. The conversion itself (turning direct links into Set/Get pairs, and restoring them) is handled by the frontend web assets plus the converter node, per the pack's changelog: "AutoLink (frontend): convert direct links into compact Set/Get nodes + restore when needed."

So the practical story is: you won't hand-wire this node in a graph. You'll use the pack's AutoLink UI action on a link, and this node is what appears in your workflow JSON. If you see it in a downloaded workflow and wonder where the data flows, look for the matching Get node - the link was just hidden, not deleted.

Installing

ComfyUI Manager → search "IAMCCS", or

cd ComfyUI/custom_nodes
git clone https://github.com/IAMCCS/IAMCCS-nodes.git

Restart ComfyUI - the frontend assets live in the pack's web directory, so a restart (and a hard refresh of the browser tab if it doesn't show up) is required for the AutoLink UI actions to appear.

Gotchas

Because this node is virtual, the real-world failure mode is a stale frontend: you've installed the pack but the AutoLink menu action doesn't show, which almost always means the browser cached the old ComfyUI frontend - hard-refresh, don't just reload. Also, be careful dragging these around manually; since they carry no actual data on the backend, a Set/Get pair that gets separated or re-created by hand can leave a workflow that validates fine but doesn't route the signal. The restore feature exists for a reason - use it rather than hand-wiring the pair.