Nougan Get (Remote) 📥

NouganGet is the receiver for the remote-data pair in Winnougan's Nougan_Nodes suite. A NouganSet stores a value under a key; this node fetches it back - no wire between the two, no matter how far apart they are on the canvas. If you've ever dragged a connection across half a workflow to reuse a seed or a model, you know the pain this removes.

How it works

When a Set node runs, it writes key → {value, color, node_id} into a thread-safe global dictionary on the ComfyUI backend. NouganGet reads that dictionary by key. The clever bit is the frontend: the key dropdown is populated by scanning the graph for live Set nodes, so you select set_lora from the list instead of typing a magic string - and the Get automatically inherits the Set's color (wires and badge included), live-updating when you change the Set's color. It's type-agnostic: whatever you stuffed into the Set - image, latent, string, model - comes out the value output unchanged.

Because the state is process-global, the Get doesn't need to be wired to the Set at all. It only needs the Set to have executed at some earlier point in the session.

The inputs that matter

Exactly one: key - the dropdown of available Set keys. Until you pick one it sits on select a key..., which is a deliberate placeholder that errors if you try to run it, so you can't accidentally read from an unset key.

Output: value (type *), the stored data, wired wherever you need it.

Installing

Search Nougan in ComfyUI Manager, or:

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

No dependencies. If the dropdown ever stops populating, click it to trigger a refresh, and hard-refresh the browser if a pack update changed the frontend - ComfyUI's JS cache is a notorious source of "why is my node stuck."

Where people get burned

The same ordering rule that governs Set: the Set must run before the Get, or you get a Key 'set_x' not found ValueError. This bites most when the Get is in a branch that executes before the Set's branch - check execution order, not the spelling, first. Keys are case-sensitive, and the state is session-only, so a Get with no matching Set after a restart is expected, not a bug. The one thing the Get will not do is create data - if there's no Set, there's nothing to get, and the error is the feature telling you so. For graphs that outgrow one screen, it's the tidy answer to wire-spaghetti.