RedNode Grabber

Subgraphs are ComfyUI's way of keeping a big graph readable - but the moment you put nodes inside one, you face the boundary problem: how do values get out? RedNode Subgraph Receive is the reading end of the pack's answer. Name it a channel and it lists every value any RedNode Sender has put on that channel - with its type and where it came from - and gives each a socket you can wire out. Nothing is wired through the subgraph boundary by hand.

The important thing about this pair is what the description says next: both ends are gone by the time the graph runs. They're replaced with ordinary links. There's no channel system running at execution time, no race, no ordering to get wrong - the Sender/Grabber pair is spliced into real wires just before the run, and ComfyUI's normal execution order takes over. That's the design that makes this different from every "wireless node" that stashes a value somewhere and hopes the ordering works out. Here there is no stashing at all.

How it works

You add a Grabber and set channel to a name. Everything any Sender has put on that channel is listed in the panel, and each listed value gets a value_1 … value_64 socket. Wire whichever you need out into the subgraph's logic. Since a channel is a group, several Senders can feed one channel and a single Grabber picks up all of them - that's the "one reader lists everything on a channel" pattern.

A channel name is just a string (up to 64 chars, trimmed). The Sender's publish flag controls scope: off means the values stay within the subgraph they sit in, on means the channel is offered further out too. Off is the safe default - with it, two instances of one subgraph won't both claim the same name.

The inputs and outputs

• channel - the channel to read.
• config - panel state; edited on the node.

Outputs: value_1 through value_64 - one socket per value on the channel, any type, wired out as needed. The panel lists each with its type and origin so you know which socket is which.

Installing it

git clone https://github.com/RedNodeAI/ComfyUI-RedNodeStudio.git ComfyUI/custom_nodes/ComfyUI-RedNodeStudio

Restart ComfyUI, or search RedNode Studio in ComfyUI Manager. No pip deps, no models. Python 3.10+.

The honest notes

The pack flags Sender/Grabber as a prototype, so treat it accordingly - the splice is plain data work and the concept is sound, but it's not battle-tested the way the Studio's core nodes are. Two practical rules: keep the channel name identical on both ends (it's exact-string matching, and a trailing space is a silent "why is this empty" bug), and remember a Grabber only sees what a Sender has put there - no sender, no sockets. If you're wiring something complex out of a subgraph, this is genuinely cleaner than a wall of Get/Set nodes; just keep the prototype status in mind for production workflows.