AnyPreviewPause

AnyPreviewPause is the flagship of the ComfyPanel pack - the README calls out its "pause and preview" integration as the headline interactive feature, and for once the marketing is accurate. It's exactly what the name says: AnyPreview and AnyPause in one node. It shows you what's on the wire, then stops the whole queue until you've had a look.

The workflow it enables is the reason ComfyPanel exists. You're in Photoshop, a generation reaches this node, and the panel freezes the run while the result lands in the PS preview. You can edit it - and this is the part that goes beyond a plain pause - the frontend lets you tweak the image, edit the text, even trim audio, and those edits are written back into the node's output before the run continues. The backend literally saves the pause state to PAUSE_REQUESTS keyed by node id, and when you hit resume it merges your edited_text, images, and audio_edits back into the returned values. Downstream nodes then run on your edited data, not the original. That's the "interactive re-edit" ComfyPanel Pro advertises, and it's genuinely different from muting a branch or flipping a switch.

It inherits the pause machinery from the same PauseMixin as AnyPause, so the mechanics and the costs are shared: it blocks on a threading.Event, releases only when a POST to /ComfyPanel/resume_pause arrives, and its IS_CHANGED returns float("NaN") while in pause mode - meaning it always reruns and drags its upstream with it. In practice that's fine here, because this is a deliberate interactive checkpoint, not something you leave in a headless batch. Where people get burned is dropping it into a workflow and running from the API or a queue you aren't watching: nothing posts to resume, and the queue just... waits. Forever, with no timeout.

Inputs and outputs are identical in shape to its two parents: no required inputs, ten *-typed passthrough outputs (output_1 … output_10), everything passes through as a list, padded with empty lists for the ports you didn't wire. The node is also marked an output node, so it always runs when its path is reached. The only real setting you'll touch lives in the frontend, not the node - the pause action and the edits are driven from the panel.

Installing it

Install once, use everything:

cd ComfyUI/custom_nodes
git clone https://github.com/Ginolazy/ComfyPanel
# restart ComfyUI

Or search "ComfyPanel" in ComfyUI Manager. No model downloads; the pack's requirements (torch, opencv, scipy, kornia, requests, aiohttp) are standard. To get the full re-edit experience you want the Photoshop 2025+ plugin too (comfypanel.ccx), because the editable preview lives in the PS panel - in plain ComfyUI the node still previews and pauses via the included frontend extension, but the "edit the image and continue with the edit" loop is a panel feature.

Honest verdict: if you only ever run ComfyUI unattended, this node will just stall your queue and annoy you. If you do interactive design iteration - especially inside Photoshop - it's the single most distinctive tool this pack ships, and the reason to install it at all.