RedNode Selector

ComfyUI gives you dropdowns on nodes that ship with dropdowns, but there's no stock node that says "here are my own five choices, pick one, hand it to the graph." RedNode Selector is that node: you type your choices, one per line, and it turns them into a dropdown whose selected value comes out as a string. Wire that into any STRING or prompt input and you've got a reusable picker - aspect ratios, style presets, subject names, anything you find yourself retyping.

It's a plumbing node in the purest sense - it touches no pixels and adds no generation capability. What it buys you is that a value that used to live as text you retyped now lives in one dropdown you can flip without touching anything downstream. That's the whole job, and it does it without any wiring ceremony.

How it works

Two inputs, and the second is the interesting one:

• choices - one choice per line. Blank lines and # comments are skipped.
• selected - the picked choice. This is the dropdown, populated automatically from the lines above.

The Label: value format is the feature to know about. A line like Close-up: extreme close-up, face fills frame shows the short label "Close-up" in the dropdown but outputs the longer value - so you get a tidy menu and a verbose prompt fragment on the wire. A plain line is used for both label and value.

The single output, value, is the selected string, ready to wire into any STRING input - a prompt box's text, a combine node, a control input.

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 dependencies, no model files, Python 3.10+.

The honest take

It's one of those nodes that looks too simple to matter until you have a list of ten prompt fragments you keep pasting. The Label: value split is the part people miss - once you realise the dropdown can show tidy labels while emitting verbose strings, you'll start using it for every list you own. Two minor notes: choices are edited on the node itself, so a selector you reuse across workflows carries its list with the workflow file (not globally), and there's no searching or grouping - if you need a thousand-choice picker with categories, this isn't that. For the 90% case - "let me pick which of these six styles to run" - it's exactly right.