Comfy-Org / Comfy-Org/ComfyUI

New API, using polling task ID to obtain accurate progress

Open
#4,855 1 comment 2 reactions 0 assignees View on GitHub
Feature
Dominant language
Python
Stars
133k
Forks
15.7k
Avg merge
1d 6h
Merged PRs (30d)
155

Description

### Feature Idea

When we use the Comfyui API, WS cannot accurately return progress, just like the Comfyui page ([rgthread-Comfy](https://github.com/rgthree/rgthree-comfy) node)

### Existing Solutions

I used a rudimentary level of code to modify and implement similar effects in executors. py and servers. py (it seems that the results are not very accurate, please correct me)
[add CF progress API.zip](https://github.com/user-attachments/files/16925997/add.CF.progress.API.zip)
After covering, use [http://127.0.0.1:8188/api/node_status](http://127.0.0.1:8188/api/node_status) Can be viewed (continuously polling)

### Other

I hope to have direct support in Comfyui, thank you

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the proposed changes in executors.py and servers.py, then compare them with the existing WebSocket progress behavior and the /api/node_status polling endpoint. The issue is complete when ComfyUI directly supports obtaining accurate progress through a task ID, with the API behavior and accuracy requirements clarified and verified.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api, backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.