Pause Workflow (Sound)

Same checkpoint, now with a chime

Pause Workflow (Sound) is exactly what it sounds like: the same pause node as Pause Workflow, but it plays a notification chime when it fires. The workflow reaches the node, everything stops, and you get pinged so you actually notice. Every input, output, and button is identical to the base node - the entire difference is one bundled notification.mp3 playing in your browser.

If you've ever started a long upscale or video pass and wandered off, only to come back to find it finished twenty minutes ago (or, worse, generated garbage at full cost), you know the appeal. It exists because a pause you have to be staring at is only half a pause. This one turns the checkpoint into a "come back, there's a decision to make" alert.

How it works

In the source it's a one-line subclass of PauseWorkflowNode - the Python side adds nothing. All the sound logic lives in the pack's JS extension: when the paused event arrives, the frontend calls new Audio(...) on the bundled mp3 and plays it. That's it. The mechanism underneath is the same synchronous block as the base node - a Python loop waits, the Continue/Cancel buttons on the node flip a flag via the pack's local endpoints, Cancel raises ComfyUI's interrupt and kills the prompt, and your two * pass-throughs (any1 required, any2 optional) come out the far side identical to what went in.

No models to download, no API key, no requirements.txt - one Python file, one JS file, one mp3, MIT license.

Install

ComfyUI Manager, search ComfyUI-pause, install, restart. Or manually:

cd ComfyUI/custom_nodes
git clone https://github.com/wywywywy/ComfyUI-pause.git

Restart ComfyUI and it shows up in the utils category. Since it's the same pack as Pause Workflow, you get both nodes either way.

The catches

The chime plays in the browser, so it only helps if a browser tab is actually open on your ComfyUI instance. Autoplay-blocked or muted tab, and you get silence. And remember the one real limitation of the whole pack: this blocks the execution thread while it waits, so if no one is around to click Continue it sits there until you are. The sound makes that less tragic - you'll know it's waiting - but it doesn't make it not true. If you need to pick which images from a batch to keep rather than a straight continue-or-cancel, reach for cg-image-filter instead. For a "stop here and let me look at the result before the expensive pass" gate you can hear from the kitchen, this is the one.