Bus Group (Mute + Solo) (frontend-only)

The display name is brutally honest: "Bus Group (Mute + Solo) (frontend-only)." This node has zero inputs, zero outputs, and does nothing on the backend - the whole behavior lives in JavaScript in the ComfyUI frontend. So why is it in the graph at all? Because ComfyUI serializes nodes, not widgets. If you want a mute/solo bus controller to exist in a saved workflow so other people (or future you) get it back when they load the file, it has to be a node.

How it works

The Python class is a stub - INPUT_TYPES returns an empty dict, RETURN_TYPES is empty, and the function is literally called noop returning nothing. The real behavior is implemented in web/iamccs_bus_group.js, which registers the frontend extension: a small controller with mute and solo toggles that let you silence or isolate groups of nodes in the graph without deleting wires. The README's release notes group it with the "frontend quality-of-life" work - Bus Group with MACRO settings arrived alongside the MultiSwitch and HW-probe UX polish in v1.3.4.

Why you'd use it

Two reasons, both legitimate. First, graph hygiene on big multi-timeline workflows: when you're testing a shotboard pipeline with dozens of segments, soloing one branch so you can see what it does without running the whole graph is genuinely useful, and mute lets you park a branch you don't want executing. Second, sharing: because it's a node, it round-trips through workflow JSON. Grab the pack's reference workflow, and the bus group comes along as part of the graph instead of being a browser-state thing you have to explain in a README.

The honest caveat: it does nothing without the pack's frontend extension active. If you load a workflow containing IAMCCS_bus_group in a ComfyUI that doesn't have IAMCCS-nodes installed, the node will complain about a missing custom node (ComfyUI marks it red) even though there's no real computation to miss. Install the pack, restart, and it works.

Install

This is the pack where install actually matters, because the frontend file has to be served:

• ComfyUI Manager → search "IAMCCS" → install → restart ComfyUI (a full restart, not just a refresh, so the JS extension loads).
• Or:

cd ComfyUI/custom_nodes
git clone https://github.com/IAMCCS/IAMCCS-nodes.git

Then restart ComfyUI. Requirements: ComfyUI ≥ 0.3.0, Python ≥ 3.12, Torch ≥ 2.8. No models, no dependencies - but if it "isn't showing up," you're probably running a cached frontend; hard-refresh or restart once more.