Stop

ComfyUI's cache model means nodes don't re-run unless their inputs changed, which is great for speed and maddening when you just want something to execute. Stop is the blunt instrument for that problem: drop it into a graph, wire anything into it, and it halts execution right there - while passing the input straight through. It's a breakpoint you can put anywhere, and it doesn't even have to be at the end of the workflow.

The mechanism is comically simple and that's the point. The input socket is wildcard-typed, so it accepts any data type, and on execute the node does two things: calls nodes.interrupt_processing() - the exact interrupt the stop button triggers - and returns the input unchanged on its output. So you can insert it mid-graph as a hard stop, and because it passes data through, you can also leave it wired inline and it's just a dead stop that happens to forward your value. If you want execution to pause somewhere but you don't want to hold up data flow, this is the node to reach for over the manual stop button, which has no input.

How it works

• input - any value. Wildcard type, so model, latent, string, image, whatever.
• output - the same value, forwarded untouched.

That's the entire schema, and it's one of those nodes that reads trivial and turns out to be quietly load-bearing. The interrupt fires regardless of what's on the input; the input is just the thing you're inspecting or carrying.

Where it fits

Three real uses. First, debugging: you want to confirm a branch works before the rest of the graph runs, so you place Stop right after it. Second, condition-adjacent checks: run a graph up to a point, stop, change something, re-run the tail. Third, as a lazy checkpoint in a long video or batch job - stop before the expensive part while you sanity-check the cheap part. It's the unconditional sibling of Show Any Stop and Show Text Stop, which only halt when their review toggle is armed; Stop halts every single time, so it's the one you consciously remove.

Installing it

Ships in ComfyUI_Eclipse:

git clone https://github.com/r-vage/ComfyUI_Eclipse custom_nodes/ComfyUI_Eclipse

Or ComfyUI Manager → search "ComfyUI_Eclipse" → install, restart. No models or extra Python packages.

Gotchas

The obvious one: this node always stops. It's not a toggle, there's no boolean - if you forget it in a shared workflow, every queue run dies at that point. Use it deliberately and delete it when you're done. One pack-level note: Eclipse v4.0.0 removed all the legacy RvTools-era node IDs, so old workflows referencing the pre-cleanup names will show red nodes until you run the included migration tool; fresh workflows are fine.