Shima Highway End Bypass

Of all the nodes in Shima's Highway routing family, this is the one that looks most like it does nothing - because mechanically, it does almost nothing. Highway Bypass Terminator takes any signal in and passes it straight out. No state, no branching, no logic. Its entire job is positional: it marks the end of a bypass segment so the frontend knows where the road stops.

That sounds trivial until you've built a graph with a few Highway Bypasses in it. The bypass system is a visual routing mechanism - the frontend draws a road that carries the signal around a chain of nodes. Without a defined end, that routing can keep propagating past the segment you meant to contain, muting nodes you wanted to keep live or sending data somewhere you didn't plan. The Terminator is the firewall: place it after a chain and the bypass traversal halts at that boundary. The source docstring says it plainly - "acts as a 'firewall' stop-point for the Highway Bypass system." If the Bypass is the on-ramp and the Detour/Merge are the interchange, this is the gate at the property line.

Inputs and outputs are each one:

• data (type *) - any signal. It's optional, so the node works even with nothing wired in, which is fine because it's really a structural marker.
• Output data (type *) - exactly what went in, unchanged.

Where you'd actually use it: anywhere a Highway Bypass wraps a processing chain and you want to guarantee the bypass logic doesn't leak past the end of that chain into the rest of the graph. Think of a detailing segment in the middle of a larger pipeline - you want the bypass to cover just the detailer, not the save nodes downstream of it. A Terminator after the detailer enforces that.

Because its backend is a pure pass-through, there are no real failure modes of its own - but the same family caveat applies: if the visual routing is misbehaving, the fix is usually in the frontend, not the wiring. Restart ComfyUI and hard-refresh the browser if the road visuals are missing, then verify each Bypass/Detour/Terminator pair is actually where you think it is.

Honestly, if you're on a simple workflow with a single manual bypass, you can skip this node. It earns its keep once your Highway usage gets complex enough that you need hard boundaries. That's a real use, not a marketing one.

Install the pack via ComfyUI Manager (search "Shima") or

cd ComfyUI/custom_nodes
git clone https://github.com/KDB-USJP/shima_wf

then restart. No models, no downloads, no dependencies.