组忽略管理器

Open any workflow big enough to be worth sharing and you'll find groups: a block of nodes for the upscale pass, a block for the second sampler, a block for the audio branch. Turning one off means either deleting it, or Ctrl-clicking a bypass on every node inside it. This node puts those groups on a dashboard, and lets switching one off switch others with it.

What the node actually is (nothing, basically)

The node body does no computation. Its whole Python side is a noop. That's not laziness - it's a deliberate pattern: the node is a persistent panel. All the logic lives in the pack's frontend extension (web/js/group_ignore_manager.js, about 1,700 lines), and all the configuration is stored as plain JSON in the node's properties.yanhuoGroupIgnore, which means it saves and loads with the workflow, travels if you share the file, and needs no external config.

What it does

It lists the groups in your graph and gives each one an on/off switch. "Off" here means group members are set to BYPASS mode (LiteGraph mode 4); "on" sets them back to ALWAYS (0). That's identical to what right-click-bypass does to a single node, just applied in bulk - the nodes aren't deleted, they're passed through. Which is the reason this class of node exists at all: if you've ever bypassed a marker node by accident you know the difference between "skipped" and "gone" matters.

On top of the toggle:

• Custom group lists. You can curate which groups the panel manages rather than accepting everything, drag to reorder, and filter by group colour - so a colour-coded workflow can hand one section to this panel.
• Linkage rules. For each group you can configure what happens to others when it turns on, and when it turns off. Rules come in two independent categories (组开启时 / 组关闭时), and within a category the group dropdowns are mutually exclusive - a group already claimed by one rule won't appear in another dropdown in the same category. That's a real design decision, not a limitation: it prevents you from writing two contradictory rules that both try to own the same group. Adding a new rule with the "+" button pre-selects the first unclaimed group in that category.
• A deliberate refusal to reach inside subgraphs. The frontend comments are explicit that it does not recurse into subgraph internals to flip their nodes' modes, because a subgraph node's own mode already governs the whole block, and quietly rewriting the inner nodes would clobber a NEVER or a manual bypass you set yourself. That's the correct call, and it's rarer than it should be.

Where it sits in the ecosystem

The incumbent for this job is rgthree's Fast Groups Muter and Fast Groups Bypasser, and they're the ones most people already have. So is a certain amount of pain: when ComfyUI's Nodes 2.0 frontend rewrite landed in late 2025 it broke a set of third-party rendering paths, rgthree's among them, and that pack's author publicly declined to port what broke. The community's reaction - a thread titled around the fear of it, and users ripping a hundred instances of a broken node out of a working workflow to be safe - tells you how load-bearing these little dashboards are.

That's the gap a pack like this one is standing in, and also the caveat. A third-party DOM-widget panel is exactly the kind of thing a frontend rewrite disturbs. If you're on the legacy canvas, expect it to behave; on Nodes 2.0, verify the panel renders and the switches actually flip nodes before you build a workflow around it. The pack's frontend does the things the platform requires for a custom panel - it marks its widget as non-serializing and calls canvas.setDirty plus graph.change() after mutating modes, because without that last bit the mode changes but the node visuals and the workflow dirty flag don't update. A nice tell that the author hit the bug and fixed it rather than shipping the naive version.

Install

One of 16 nodes in yanhuo-easy-use (category yanhuo, MIT, Chinese UI). Manager → search the pack title, or:

cd ComfyUI/custom_nodes
git clone https://github.com/yanhuoxunxianren/yanhuo-easy-use
# restart ComfyUI

No pip install (the pack declares no dependencies) and no model files. Because the useful half of this node is JavaScript served from the pack's web directory, hard-refresh your browser tab (Ctrl-Shift-R) after installing or updating, otherwise the canvas may load a cached extension set and the node will appear as an empty box.

Common issues

Empty node, no panel. Almost always the frontend extension didn't load. Hard-refresh the browser; if it persists, check the browser console for an import error and confirm the pack's web/js folder survived your install.

"My switches do nothing." The panel writes node modes directly on the LiteGraph objects, so it needs the graph to be in a state where those changes stick - the frontend relies on graph.change() to mark the workflow dirty. If you're running a heavily modified or very old frontend, behaviour is on you.

"It ignored a group inside my subgraph." Intentional. Manage the subgraph node itself.

"My group won't come back on." The panel treats a group as on if any member node is ALWAYS. If something else - the frontend, or another extension - is setting modes behind it, you get a tug of war. Turn off other group managers while testing this one.

For rgthree's role here, the Fast Groups nodes, and the ongoing Nodes 2.0 situation, read docs/knowledge/comfyui-ecosystem.md. The taxonomy of legibility nodes - reroutes, bookmarks, group muters, and why they're not the same thing as a context bus - is in docs/knowledge/comfyui-node-plumbing.md.