Skip to content

v0.0.5 — the relay ships with the installer

Choose a tag to compare

@an80sPWNstar an80sPWNstar released this 13 Aug 03:32
· 29 commits to main since this release

If you installed 0.0.4, install this one. That build shipped without the ComfyUI relay node,
so there was no way to enable step progress and nothing telling you it existed.

The relay now comes with the app

comfyui-relay/ installs alongside the app (in resources/comfyui-relay/) instead of being
sealed inside the application archive, so you can actually copy it where it needs to go.

On first launch the app now explains the one manual step, shows you the exact folder on your disk,
and gives you a button to open it. Afterwards it lives behind the (i) button in the top bar.

The step itself: copy that folder into <your ComfyUI>/custom_nodes/comfyui-watcher-relay/ and
restart ComfyUI. Its log prints comfyuiWATCHER progress relay installed. Repeat per ComfyUI
host. Training (ai-toolkit) hosts need none of this.

Why it is needed at all

ComfyUI sends step counts only to the client that submitted a job, so a passive watcher never sees
progress for anything queued from the ComfyUI web UI. The relay rebroadcasts those messages under
a watcher.-prefixed type that ComfyUI's own frontends ignore.

Without it a card still shows the host, queue, model, and whether a job is running — but no
step X/Y, rate or ETA. It shows an indeterminate sweep rather than inventing numbers.

It tells you whether it worked

The setup panel reports each ComfyUI host as relay active, no relay — steps unavailable, or
unknown until a job runs. Any watcher.* message is proof the relay is loaded, since nothing
else emits them. "No relay" is only claimed after a job has been running for ten seconds in
silence — an idle host stays unknown rather than being accused of a missing relay.

Downloads

  • WindowscomfyuiWATCHER Setup 0.0.5.exe
  • LinuxcomfyuiWATCHER-0.0.5.AppImage or comfyuiwatcher_0.0.5_amd64.deb