Do Nothing Node (Bridge)

The do_nothing function in this node's source is five lines long and its only instruction is "hand it back." That is the whole feature. If you're here because a workflow you downloaded has a node called "Do Nothing Node (Bridge)" sitting in the middle of it, connected to nothing that looks like it should matter - nothing is broken, and nothing is being wasted. There are exactly two reasons people wire this in, and both are legitimate.

First, the naming situation, since it wastes everyone's time: the class is LTX2PassThrough, the README calls it "Image + String Bridge," and the display name is "Do Nothing Node (Bridge)." Search any of the three and you'll find it. It lives under Silicon-Implants/Utilities - and despite the name, no special relationship to LTX-2 or to Apple Silicon.

What it actually is

It's a plumbing node - the value nodes, switches and reroutes that touch no pixels and make up most of any real workflow. This one is the simplest member of that family: image in, same image out, string in, same string out. No copy, no resize, no encode. Same Python object both ways.

How it works is the point. ComfyUI decides what to run and when by walking backwards from output nodes and executing each node only once all of its inputs are ready. So a node that consumes two things - an IMAGE and a STRING - and emits both is a junction that makes the downstream path wait for both branches. That gives you the two real uses:

• Keeping a label attached to an image. A filename pattern, a shot ID, a prompt tag - it needs to reach a downstream save or text consumer without dragging a second wire across the canvas. Both travel in, both come out side by side.
• Making a text-only branch wait for the image branch. Routing through here creates a dependency edge that didn't exist before.

That second use is the sharp edge: ComfyUI has no explicit execution order, only dependencies, so this node adds one edge and sequences nothing beyond it.

Inputs and outputs

Two in, two out, and nothing else - no optional sockets, no hidden switches:

• image (required, IMAGE) - the picture you want to carry through.
• text_label (required, STRING, default "Input text here") - a text box you can type into directly, or convert to an input and wire from any upstream string.
• image and text_label out - same types. Wire the image to whatever consumed the image before, and the string to whatever wants the label downstream.

Installing it

It ships in blackest/Silicon-Implants, a three-node Mac-flavoured pack. Via ComfyUI Manager, search Silicon-Implants. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/blackest/Silicon-Implants comfyui-silicon-implants

Restart ComfyUI and hard-refresh the tab. There's no requirements.txt in this repo and this node pulls in nothing - no models, no downloads. The pack's other nodes want Apple Silicon and, in one case, city96/ComfyUI-GGUF; this one is plain Python and runs the same on CUDA, ROCm or CPU. It just isn't why you'd install the pack.

Where people get caught

The pack loads as a unit. __init__.py imports all three node modules at startup, so if a sibling breaks, this node disappears with it - an empty "Silicon-Implants" category is usually a GGUF problem, not a bridge problem. That loader says so in its own error: "requires city96/ComfyUI-GGUF to be installed and enabled."

A few more things worth knowing:

• It's a single-commit repo from September 2026. If Manager's index hasn't caught up, the clone above is the route.
• It doesn't defeat ComfyUI's cache - no IS_CHANGED override, so if nothing upstream changed, nothing downstream re-runs. Editing the typed label changes the label, not the picture.
• It can't rescue a dead branch. If the node feeding text_label never executes, this node never executes, and whatever consumed the label doesn't either.
• Don't expect an MPS speedup. The README is blunt that this one is "not MPS-specific - just a small utility that lives here." The Mac work in this pack is in the CLIP loader and the Gemma encode node.

Should you use it

If you're already running the pack on an M-series Mac, sure - it's free, it's inert, and it's a tidy place to park an image-plus-label pair. If you're on a PC and this is your only reason to install a one-person Mac node pack, use an rgthree reroute (one wire, sized how you like) or a Context node if you're bundling many connections. There's a long-running grumble about nodes that hide wires and make graphs unreadable. A bridge you can see is fine; forty of them is a debugging session.