Group Scopes

Group Scopes was the gatekeeper of the old WorkflowX config system. While a Group Configurator said what each group should be per profile, Group Scopes said which groups the config system governed at all - mapping each ComfyUI group name to a scope like "Group Configurator", "Selector Mute", "Selector Bypass", or "Ignore". Groups marked Ignore were off-limits; config switching left them alone.

It's deprecated, like the rest of that legacy family. The pack keeps it registered so old workflow JSON loads, and the docs tell you to rebuild with Config SelectorX - whose Scopes editor is literally this node's job folded into one place.

How it works

Group Scopes has a single input, scopes_json, a frontend-managed mapping of group names to scope names. The node validates that JSON when it runs - each value must be one of the four scope options - and does nothing else. It has no outputs, no function beyond being a state holder.

The real work happened in combination with the other legacy controllers. At queue time, WorkflowX's resolution machinery read the workflow JSON: Group Scopes told it which groups were governed and how (by config modes, by selector mute, by selector bypass, or not at all), a Config Selector named the active profile, and Group Configurator supplied the per-profile modes for governed groups. Then the Get nodes resolved Set values from groups that were Active for that profile. Three nodes, three pieces of state, plenty of ways to get them out of sync - which is precisely why the author collapsed the whole thing into Config SelectorX's single selectorx_state.

Inputs

• scopes_json (STRING) - frontend-managed group→scope mapping. Read-only for you.

That's it. There isn't even a required input on the node.

Migrating off it

Same recipe as every legacy configurator: load the old workflow, note the group-to-scope assignments and the named configs, add Config SelectorX, recreate the scopes in its Scopes editor and the modes in Configs, verify every typed Get and Relay consumer still resolves, then delete the legacy nodes and save under a new filename.

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

• "scopes_json contains invalid scope" - a hand-edited value isn't one of the four scope names. Reset through the UI.
• Config switches aren't affecting a group. That group is probably marked Ignore in scopes_json - the config system is deliberately leaving it alone.
• Old workflow, moving nodes breaks resolution. Legacy group membership is geometric (node rectangle vs. group rectangle), so dragging nodes around can quietly change what a scope covers. Config SelectorX avoids this.

If you're reading this because you're about to build with Group Scopes: stop, use Config SelectorX. If you're reading it because you inherited a workflow: the migration is mechanical and the repo documents it step by step.