🌊Bypass Nodes w Groups by ID
The remote control deck for your whole workflow's switches
There comes a point in every big workflow where you stop editing it and start operating it. You're testing whether this upscale path or that refiner really helps, so you're muting and bypassing nodes ten times a minute, hunting across a canvas the size of a city. Trix Bypass Nodes w Groups by ID (TrixBypasser) is the answer to that specific kind of annoying: one node sitting anywhere on the canvas that remotely flips bypass/mute on the nodes you've told it about, organized into collapsible groups.
It's a dashboard node, in the same family as rgthree's Fast Groups Muter and Bypasser - the "make a graph too big to read into one you can still work in" school of thought. The difference is the targeting. Where rgthree keys off group boxes on the canvas, Trix keys off node IDs. You right-click any node (or group, or multi-selection) and hit "Copy Node ID" / "Copy Selected Node IDs" / "Copy Group Node IDs" - context menu entries this pack injects - then add those IDs to a target in the node's picker submenu. From then on, one toggle on the deck controls all of them.
How it actually works
Here's the part that surprises people: the Python side is a total no-op. TrixBypasser has no inputs, no outputs, and its FUNCTION is literally do_nothing. All the real work happens in web/trix_bypasser.js. The node stores its targets as node IDs in its own serialized properties, and when you flip a switch it walks app.graph.getNodeById(...) and sets each target's node mode - 0 for normal, 2 for mute, 4 for bypass, depending on your mute/bypass toggle. It remembers each target's original mode and restores it the moment you untarget that node, so it never permanently clobbers anything.
You get the whole control surface without touching the data flow: searchable picker to add targets, per-group collapsible decks, a single/multi selection mode, the 👁 button that instantly centers your canvas on the target nodes, and a ⚠️ indicator that pops up when a target ID no longer resolves. Click that warning and you get a recovery modal to re-bind the target to a different node instead of silently breaking. The pack also remaps target IDs when you collapse nodes into a subgraph - genuinely thoughtful, since that's normally where remote setups die.
Inputs and outputs
None. Not "a couple" - the schema is empty. This is a pure control surface: it wires nothing into your graph and needs no wires into it. If you find yourself trying to connect it to something, you're using it wrong. It just needs to exist on the canvas.
The tradeoff you should know about
ID-based targeting is the pack's whole bet, and it cuts both ways. Re-import a workflow, copy-paste nodes, or let a target node get deleted, and those IDs change or vanish - which is exactly the failure mode the ⚠️ recovery modal exists to patch. If you want something that survives node renames and re-imports more gracefully, rgthree's group-box approach is the more battle-tested choice, though its maintainer has openly declined to port to ComfyUI's Nodes 2.0 frontend. This pack's JS logs "Nodes 2.0 compatible" - the author is explicitly chasing that. It's young, and the only real community signal so far is the author's own launch post, so treat the polish as a promise you're beta-testing.
Install and troubleshooting
Install via ComfyUI Manager (search ComfyUI-TrixNodes or publisher trix7111), or manually:
cd ComfyUI/custom_nodes
git clone https://github.com/trx7111/ComfyUI-TrixNodes
Then restart and hard-refresh the browser. No pip dependencies, no model downloads - it's all front-end, so it installs in seconds. One trap: the README's own manual clone line still points at github.com/pixaroma/ComfyUI-TrixNodes, which 404s (stale handle from the author's earlier alias). Use the trx7111 URL above or let Manager do it.
If the deck renders as a blank/empty node, the extension JS didn't register - check the browser console for errors and hard-refresh. Everything cosmetic (colors, animations, context menu options) lives in Settings → Trix Nodes.
Inputs (0)
No inputs
Outputs (0)
No outputs