SSG Smart Tag

SSG Smart Tag is the quietest node in the SSG Smart Suite, and the easiest to skip - which is a shame, because it's the one that keeps the whole "autonaming" system honest. When you drop a wire onto a Pipe, Satellite, Vault, or any other dynamic SSG slot, the frontend crawls upstream to figure out what to call that lane. That crawl (findTrueUpstreamAnchor in the source) checks, in priority order: an explicit SSG Smart Tag, a custom-renamed node, known multi-output maps like CheckpointLoaderSimple, subgraph input proxies, and finally the raw data type. The Tag sits at the top of that priority list. Drop one between a node and your SSG bus and its tag_name becomes the lane's label, overriding whatever the engine would have guessed.

That's the whole reason it exists. Wireless buses have a legibility problem - with no visible wire, "which output of which node is this?" is genuinely harder to answer, the same trade-off the KB's plumbing doc flags for every wire-hiding convenience node. The Tag is the pack's mitigation: it's a hard naming boundary and an explicit type-caster, so a lane feeding a Face Detailer shows up as face_detailer instead of MODEL_3 in every Satellite and in the HUD.

Functionally it's a pure passthrough. Three inputs, one output, all trivial:

• input (wildcard *) - the signal you're labeling. Accepts anything.
• tag_name (string, default Tag_1) - the label the autonaming engine uses for this lane. Set it to something you'll recognize.
• type_override (enum, default AUTO) - force the lane's type: *, MODEL, CLIP, VAE, LATENT, IMAGE, MASK, CONDITIONING, INT, FLOAT, STRING, or BOOLEAN. AUTO lets the engine infer from the upstream node.

The single ◦ output just echoes the input through untouched - the node does no processing. Its only job is metadata for the naming drill, which is why it's the one SSG node with no channel registry involvement at all. It's also the only node in the suite where the inputs are genuinely self-explanatory, which is refreshing.

Where you'd use it: any time you care what a Satellite's tracks get called, or when the engine's auto-name is ambiguous (two loaders, same type, feeding the same bus). Sloppy lane names are the #1 way wireless workflows become impossible to read, and this is the cheap fix. It's a 30-second add that pays off the moment you open the HUD.

Installing it

cd ComfyUI/custom_nodes
git clone https://github.com/SgtSauv/ComfyUI-SSG-Smart-Suite.git

Restart, or install via Manager by searching "SSG Smart Suite". No models, no Python dependencies (requirements.txt: "No external dependencies"), just the pack's console boot banner.

Common issues

• The lane name didn't change → the Tag has to be the first thing the upstream crawl hits. Put it directly between the source node and the SSG slot; if another Tag or a renamed node sits above it, that one wins.
• Tag does nothing visible → correct. It's metadata, not a processor; the effect shows up in Satellite track names and the HUD.
• Thin support → this suite has near-zero Reddit presence as of 2026; GitHub issues is the realistic path.