Nougan Set (Remote) 📡

ComfyUI's wires are great until a graph gets big enough that a connection has to stretch across the whole canvas, over other nodes, and you're dragging it by feel. NouganSet is the "wireless" answer from Winnougan's Nougan_Nodes suite: you store a value under a named key, and a matching NouganGet node anywhere else in the graph retrieves it. No long cables, no rerouting.

How it works

The node keeps a thread-safe global dictionary (_NOUGAN_REMOTE_STATE, lock-protected) that lives for the duration of the ComfyUI session. When NouganSet runs, it writes key → {value, color, node_id}. A NouganGet with the same key reads it back, keyed by exact, case-sensitive string. Because it's a process-global, the two nodes don't need to be in the same subgraph - or even the same tab - as long as the Set executes before the Get.

Two niceties make it feel polished. Keys you type are auto-prefixed (lora becomes set_lora), which keeps remote keys from colliding with anything else. And there's a color system: pick from 14 cyberpunk-named colors (Neon, Plasma, Toxic, Blood, Quantum, Gold…) and the Set's title bar, body, wires, and badge all tint to match - with the Get node inheriting the color automatically and live-syncing when you change it. It's cosmetic, but it makes "which Get goes with which Set" readable at a glance.

The inputs that matter

• key - the identifier (auto-prefixed with set_).
• value - the data itself. Any type works: images, latents, strings, models.
• color - the visual theme, purely for legibility.

Output: pass_through - the same value you put in, so the Set can sit inline in an existing wire without breaking the flow.

Installing

Search Nougan in ComfyUI Manager, or:

cd ComfyUI/custom_nodes
git clone https://github.com/Winnougan/Nougan_Nodes
# restart ComfyUI

No dependencies. One note from the docs: after updating the pack, hard-refresh the browser (Ctrl+F5) - ComfyUI aggressively caches the frontend JS, and the remote-data UI is the kind of thing that looks broken when it's actually a stale cache.

Where people get burned

Ordering is the real rule: the Set must execute before the Get, or the Get raises a Key not found error. ComfyUI runs things in dependency order, so if the Get has no wire to the Set it's easy to end up in the wrong execution order - and the error is the symptom, not the cause. Keys are case-sensitive and select a key... (the Get's unset placeholder) deliberately errors so you don't silently read garbage. And remember the state is session-global: it doesn't persist across restarts, and two graphs in the same session sharing a key name will share a value. Colorful, type-agnostic, and genuinely useful once your graphs outgrow a single screen.