Set Node (TJ)

The core of TJ_NODE's "wireless" architecture

Set Node (TJ) is the transmitter of the pack's signature Wireless/Fake-Wire system. You feed it any value - image, model, prompt, whatever - give it a name, and it registers that value as a wireless provider. Any Get Node (or any node with an embedded Get, of which this pack has plenty) can then receive it by name, across the whole canvas, with no visible wire between them.

If you've ever opened a workflow someone built and spent ten minutes tracing a model output from a loader in the top-left to a sampler in the bottom-right, you know why this exists. Long wires are the #1 readability killer in ComfyUI, and this node is the pack's answer: keep the logical connection intact while making the visual graph clean. It's the node the whole TJ workflow philosophy is built around.

How it works

Mechanically it's almost embarrassingly simple on the backend: execute takes value and set_name and just passes the value straight through (value output, type *). The magic lives in the pack's provider registry on the frontend - the value is registered under set_name so Get Nodes can pull it by name. The output slot means you can also chain the value forward normally; wireless routing is an addition, not a replacement, for normal wiring.

The inputs that matter

Only two:

• value - the data to transmit. Any type.
• set_name - the provider's name. This is your routing map and it deserves real thought. The pack's own anti-patterns doc calls out duplicate names and garbage names (test, aaa, temp) as the things that make reconnect unstable and workflows unmaintainable. Names like MAIN_IMAGE, POS_PROMPT that read like map keys are the intended usage.

Install it

Set Node ships in TJ_NODE and has zero extra dependencies - the whole pack installs the same way:

cd ComfyUI/custom_nodes
git clone https://github.com/designloves2/ComfyUI-TJ_NODE.git

Or ComfyUI Manager → Install Custom Nodes → search TJ_NODE, then restart. Category: ✨ TJ_Node/Wireless.

Where people get burned

Three recurring traps, all around naming and reload:

1. Duplicate provider names. Two Set nodes with the same set_name and Get nodes can reconnect to the wrong one after a reload. Fix: unique, stable names.
2. "Get list is stale / missing" after rename or reload. The pack has a context-menu entry for this: right-click → TJ Node → Refresh ALL Get Nodes rebuilds the provider list. That's the first thing to try when a Get doesn't see a Set.
3. Thinking it's wireless-through-time. Values are registered at queue time from the executing graph - this is routing, not persistence. For values that must survive restarts, you want the Send/Send Point bridge instead.

One more thing worth knowing: the pack also gives you embedded Get inside many nodes (Smart Show, Save & Preview Image, the batch nodes), so you often don't need a standalone Get at all - Set once, receive locally. The author's own recommendation is to keep providers few, named well, and let the wireless layer carry the cross-section traffic while short visible wires handle what's inside a section.