Config Selector

Straight answer: this node is deprecated. Config Selector was the first version of WorkflowX's config switcher - you'd type a config name into it, and it told the pack which named configuration was active so the Get nodes could resolve the right values. It still works, and WorkflowX's Get/Set machinery still honors it, but the pack's own README says the four legacy configurator nodes exist only so old workflow JSON can load. Don't put this in a new workflow.

Why read about it at all then? Because you'll meet it in the wild. Workflows built during the pack's early days (the author's first r/comfyui release in May 2026 shipped exactly this design) still carry it, and knowing what it does is the difference between recognizing a legacy workflow and being confused by it.

How it works

Config Selector is a controller node with no outputs. It holds selected_config (the active config name) and a console_output toggle. On its own it does almost nothing - the actual decision-making happens elsewhere. When a Group Configurator node stores a mapping of group-name → Active/Bypass/Mute for a matching config name, and Get/Set nodes sit inside those groups, the resolution machinery reads all of it from the workflow JSON at queue time: find the config the Selector points at, look up which groups that config marks active, and let the Get nodes pick the Set value from an active group.

So the old system was a two- or three-node dance: Config Selector picks the profile, Group Configurator(s) hold the per-group modes, and Group Scopes controls which nodes are governed at all. Compared to Config SelectorX - which folds scopes, configs, and per-group modes into one self-contained state - it's clunkier and easier to get out of sync.

Inputs

• selected_config (STRING) - the active config name.
• console_output (no/yes) - enables resolution diagnostics.

That's it. No outputs, no state of its own beyond the name.

Migrating off it

The pack's migration guide is straightforward: load the old workflow, note the group-to-scope assignments and named configs, add a Config SelectorX, recreate the assignments in its Scopes and Configs editors, then delete the legacy controller nodes once the new state is stored - and save under a new filename, reload once, before retiring the old one. The typed Set/Get and Relay node IDs stay current; only the controller arrangement changes, so your downstream graph is untouched.

Install

It's in the WorkflowX-Configurator pack; Manager search WorkflowX Configurator, or git clone https://github.com/haroonaslam/WorkflowX-Configurator into ComfyUI/custom_nodes, restart, hard-refresh.

Common issues

• It loads but does nothing. That's expected - it's a state pointer, not a workhorse. The real behavior lives in the Group Configurator nodes and the Get resolution.
• Configs don't match. The Selector's selected_config string must match a config_name on a Group Configurator exactly.
• You're about to build a new workflow with it. Don't. Use Config SelectorX.

Treat this node like an artifact: worth one evening to understand if you inherited a workflow, worth zero minutes of your time if you're starting fresh.