RedNode Combo Control
Drive another node's dropdown without a single wire
RedNode Combo Control is the smallest member of the pack's "wireless control" family, and the author is upfront about its status: it's the stage-1 prototype for the multi-row RedNode Control Panel. It exists to answer one question - "can I change that sampler's dropdown from over here?" - and it answers it with three fields and no wires at all.
You pick a target (a dropdown filled from the nodes in your current graph), a widget (which dropdown or toggle on that node you want to control), and the value to set. The value field is itself a dropdown populated with that widget's actual choices, so you can't typo your way into an invalid option. The node has no outputs and does nothing at execution time - it's a pure frontend control. The pack's JavaScript extension reads your graph, fills those dropdowns, and writes the value straight into the target widget the moment you change it.
Why would you want this? The wiring-free idea is real: put the sampler, scheduler, and CFG toggles of a node buried inside a subgraph onto a single control you can reach without navigating. For one control, this node is the lean option - one row, three fields, done.
But be honest about the ceiling. This is a prototype, and the full RedNode Control Panel is the grown-up version: many rows on one node, search, colors, section titles, and saved scenes that apply a whole set of values at once. If you're planning to control five things, skip straight to the Control Panel. Reach for Combo Control when it's genuinely a single dropdown you want to relocate, or when you want the smallest possible footprint for one switch. The author explicitly built the bigger node to replace this pattern, and you can feel the design intent in the naming.
A note on how to think about these frontend-driven controls: they live in the browser, not in the graph's data flow. That's the point - the wires that aren't there are the feature. It also means the control needs the UI present to do its thing; it's not a backend node you can drive from an API call alone. For interactive work that's exactly what you want.
Installation is the pack, once:
cd ComfyUI/custom_nodes
git clone https://github.com/RedNodeAI/ComfyUI-RedNodeStudio.git
or search RedNode Studio in ComfyUI Manager, then restart ComfyUI. No pip dependencies. Combo Control works with any model and any recent ComfyUI - it's part of the general-purpose "RedNode" half of the pack, not the Krea 2 half, so you don't need the Krea stack to use it.
Inputs (3)
| Name | Type | Default | Description |
|---|---|---|---|
| target | STRING | Which node to control (dropdown, filled from your graph). | |
| widget | STRING | Which dropdown/toggle on that node. | |
| value | STRING | The value to set (dropdown of that widget's choices). |
Outputs (0)
No outputs