Config Selector Advanced

Config Selector Advanced is what Config Selector grew into before the whole design got replaced: the same deprecated profile-picking controller, plus a frontend-managed advanced_state field that stores per-group mute and bypass switches. It's from the generation of WorkflowX where the config system was spread across several controller nodes, and the pack's own docs now tell you not to build with any of them. Use Config SelectorX instead.

You'll still encounter it in older workflows, so it's worth recognizing. If you find one in a shared graph, your job is migration, not debugging.

How it works

Like the plain Config Selector, this node has no outputs. It holds selected_config (the active profile name) and console_output, and adds advanced_state - a JSON object managed by the frontend extension with mute and bypass sections, each mapping group names to booleans. The node validates that JSON shape when it runs (it must be an object with only mute and bypass sections of booleans), but it doesn't apply anything itself.

The actual behavior happens through the same resolution machinery every WorkflowX Get node uses. The resolution code treats both old selectors identically: it scans the workflow JSON for a Selector-type node, reads its selected_config, pairs it with the group-mode mappings held by Group Configurator nodes, and lets Get nodes pick Set values from groups that are Active for that config. advanced_state is where the earlier design kept the mute/bypass decisions that Config SelectorX now stores in its unified selectorx_state.

Inputs

• selected_config (STRING) - active config name.
• console_output (no/yes) - resolution diagnostics.
• advanced_state (STRING) - frontend-managed mute/bypass JSON. Read-only for you.

Migrating off it

Same move as for all four legacy controllers: load the old workflow, note the scope and config assignments, add a Config SelectorX, recreate everything in its Scopes and Configs editors, verify each typed Get and Relay consumer resolves, then delete the legacy nodes and save under a new filename. The Set/Get node IDs don't change, so downstream wiring is untouched.

Install

Ships in WorkflowX-Configurator - Manager search WorkflowX Configurator, or clone https://github.com/haroonaslam/WorkflowX-Configurator into ComfyUI/custom_nodes, restart, hard-refresh.

Common issues

• "advanced_state contains invalid section" - the state field was hand-edited into an unexpected shape. Reset it through the UI (or just migrate to SelectorX and delete the node).
• Doesn't switch anything. It's a pointer, not an executor - the switching behavior lives in Group Configurator mappings plus Get-node resolution.
• New workflow? Skip it. Config SelectorX is strictly cleaner.

One line of context: this whole legacy family traces back to WorkflowX's original release in May 2026, when the config system was a chain of small controllers. The author rebuilt it as the single-node Config SelectorX in 2.0. Treat Config Selector Advanced as a fossil with a migration path.