ComfyUI Node

The BUTTON

Kill the queue, restart it, or reboot everything

By traugdor·Created 3 years ago·Updated 9 months ago· 16
The BUTTON

      Sometimes you need to stop what ComfyUI is doing - like, right now, without hunting for the tiny cancel button buried in the top-right of the queue. The BUTTON (quadmoonThebutton) is a node with zero inputs, zero outputs, and exactly one purpose: give you big buttons to control the whole session from wherever your mouse already is. The author's own pitch in the README is basically "something gone wrong with your setup? Hit The BUTTON." It's a silly premise that turns out to be genuinely handy.

      What the three buttons actually do

      The node itself is a stub - a Python class with no data flow at all, plus a small JavaScript extension that paints three widgets onto it. Wire nothing; just drop it anywhere in your graph (or on its own) and click. Here's what each button does, read straight from the JS:

      • KILL or RESTART queue - calls ComfyUI's interrupt. If a prompt is running, it stops it. If you have auto-queue on, the next item starts, which is where the "restart" in the name comes from.
      • REBOOT ComfyUI - asks you to confirm, then hits the /manager/reboot endpoint and restarts the whole server.
      • START queue - queues the current prompt. The README notes this was added for third-party frontends that hide the main queue menu.

      Think of it as the panic button for a queue that's running away from you, and the convenience button for the rest.

      Where people get burned

      • REBOOT needs ComfyUI Manager. /manager/reboot is a Manager endpoint, not a core ComfyUI one. If you don't have ComfyUI Manager installed, that button quietly fails and you get an alert. KILL/RESTART and START are native and always work.
      • It has no outputs and does nothing in the graph. New users drop it in expecting a signal to appear and assume it's broken. It isn't - it's a pure side-effect node. It doesn't even get connected to anything.
      • Interrupt isn't an undo. KILL stops the current run, but whatever already finished stays in your output folder, and your queue settings decide what happens next. The README's "use responsibly" is doing a lot of work there.

      Is it worth installing for?

      Honestly, if you already have ComfyUI Manager's toolbar and never struggle to find the cancel button, this is a nice-to-have, not a must. But it earns its place in the "quality-of-life utility" tradition that packs like rgthree-comfy own - nodes that add no generation capability and exist purely so a large workflow stays workable. If you run long queues or drive ComfyUI through a frontend that buries the menu, The BUTTON is exactly the kind of small thing that makes you wonder why it wasn't core. And unlike a lot of this pack, it has no dependencies and nothing to configure - it just works.

      Installing the pack

      Install via ComfyUI Manager (search "quadmoon's ComfyUI nodes", or use Install via GIT URL with https://github.com/traugdor/ComfyUI-quadMoons-nodes.git), then restart:

      cd ComfyUI/custom_nodes
      git clone https://github.com/traugdor/ComfyUI-quadMoons-nodes.git
      # then restart ComfyUI
      

      No requirements.txt, no model downloads. If you clone manually, be aware the repo pulls in jags111's efficiency-nodes as a git submodule for other nodes in the pack - harmless for The BUTTON itself, but clone with --recurse-submodules if you want the whole pack healthy.

      CategoryQuadmoonNodes

      Inputs (0)

      No inputs

      Outputs (0)

      No outputs