OrchestratorNode Bypass autoconfig

This is the node the pack's README is actually built around - "Orchestrator (Auto-Discovery)" - and it's a different mechanic from its Group-based siblings. Instead of drawing a visual box around a cluster of nodes, you tag node titles with a bracket code, and this node builds a toggle bank by scanning for those tags anywhere in the graph.

How it works

You set it up in three steps. First, drop the node (listed in the menu as Logic > Orchestrator (Auto-Discovery)) anywhere on your canvas and give it a group_id - a name you invent, like MODELS. Second, rename any node's title to include [[MODELS:SDXL]] somewhere in it - right-click a node, or double-click its title bar, and prefix it, e.g. turn a checkpoint loader's title into [[MODELS:SDXL]] Load Checkpoint. Tag a second node [[MODELS:PONY]]. Third, the Orchestrator node scans every title in the graph for the [[GROUP:TAG]] pattern; any tag whose GROUP matches its own group_id gets a toggle, labeled with the TAG. Flip one on and that node gets mode 0 (active); every other tagged node sharing the same group gets mode 4 (bypass - skipped, but tries to pass data through where the types match). It's a radio switch: only one tag can be active per group at a time.

Untagged nodes are never touched, no matter what - worth knowing, since it's easy to assume the Orchestrator manages everything nearby rather than only the nodes you explicitly bracketed.

Want a second, independent bank of toggles? Add a second Orchestrator node with a different group_id, say STYLES, and tag other nodes [[STYLES:Cinematic]] / [[STYLES:Anime]]. It only ever reacts to its own group_id, so the two banks run side by side without interfering - the README's own worked example.

One implementation detail worth knowing that isn't in the README: the pack backs up your tagged titles to the browser's localStorage, keyed to the workflow, and tries to auto-restore a tag if ComfyUI ever assigns a tagged node a new internal id (which can happen after certain undo or paste operations). If a toggle you set up seems to vanish, it may quietly repair itself on the next load before you need to retype anything.

The inputs and outputs that matter

None - check the schema and both required and optional are empty, with no outputs. The real "inputs" live outside the node's data ports entirely: the group_id text field on the node itself, and the [[GROUP:TAG]] strings you type into other nodes' titles. There's nothing to wire.

How to install it

ComfyUI Manager: search ComfyUI_Custom_Switch, install, restart. Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/tritant/ComfyUI_Custom_Switch

restart, and you're set - no requirements.txt, no models, just torch, already part of ComfyUI. It's a small, single-author pack (built by tritant, ~16 stars, quiet since October 2025) built around exactly this trick and not much else.

There's no direct equivalent for this tag-based scheme in the bigger utility packs like rgthree-comfy - rgthree's Fast Groups Muter/Bypasser work off drawn canvas Groups, the same way this pack's own Group Bypasser/Muter do. The title-tag approach here is the actual differentiator: you can scatter the nodes you want in one switch bank anywhere across a large graph, without physically boxing them together, and run several independent banks side by side just by giving each Orchestrator node its own group_id.

Common issues & troubleshooting

No toggles appear. Check two things: the group_id on the node matches exactly what you typed inside the brackets (it's a straight string match, so a typo or case mismatch means silence), and that the bracket syntax is actually in the node's title, not somewhere else like a note or a widget value.

A toggle I built disappeared. See the localStorage auto-restore note above - reload the workflow once before assuming it's gone for good. If it's still missing, just retype [[GROUP:TAG]] into that node's title again.

Downstream complains after I switched a tag off. Bypass tries to pass data through where types match, so this usually shouldn't fully break a run - but if it does, the sibling node OrchestratorNode Muter (auto config) does the same tag-based trick with a harder off (mute instead of bypass), which is the opposite direction if you need that.