-
Notifications
You must be signed in to change notification settings - Fork 7.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Add ComfyUI tool for Stable Diffusion #8160
feat: Add ComfyUI tool for Stable Diffusion #8160
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See comments
@crazywoola Done. Check it again please. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See the author
api/core/tools/provider/builtin/comfyui/tools/comfyui_stable_diffusion.py
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See comments
Hi @QunBB . When I was testing this tools, an error shows up: Failed to get models, Please input model. My comfyui is started on http://127.0.0.1:8188/ with a blank canvas. How to resolve this error? |
@crazywoola @WeepsDanky The model name should be also exposed when verifying tool's credentials. Some modified code was after verifying credentials, so i miss the test about the changed code about |
@crazywoola @WeepsDanky I have fixed it, please check it again. |
@crazywoola But i am troubled by Ruff check, should i reformat the files? |
@QunBB Great thanks, it is working now. |
@QunBB I noticed the tool currently can only use a pre-defined workflow txt2img.json. Can you please be more specific about the name and description in yaml? We need to make sure other users understand this tool can only use this workflow. For example: |
@WeepsDanky Hi, i have change the name and description in yaml. In addition, i add the support for SD3 and FLUX. |
* commit '7f3282ec04d87cfb8fcff892e824c96094b92636': (105 commits) Update version to 0.8.3 in packaging and docker-compose files (langgenius#8590) chore: fix webpack dependencies order (langgenius#8542) ComfyUI tool use the new internal enumeration class "VariableKey" (langgenius#8533) Fix: update qwen model and model config (langgenius#8584) fix: fix qwen series model type (langgenius#8580) feat: add hunyuan-vision (langgenius#8529) chore: improve delimiter (langgenius#8552) add storage error log (langgenius#8556) feat: sync Qwen API with Aliyun Bailian (langgenius#8538) fix: thread_pool submit count in parallel workflow not releasing (langgenius#8549) fix: ci issues(missing duckduckgo-search==6.2.11, ruff lint issue) (langgenius#8543) feat: add format util unit and add pre-commit unit check (langgenius#8427) validate user permission before enter app detail page (langgenius#8527) refactor: rename task_type to task for jina embeddings v3 (langgenius#8488) chore: Deprecate gpt-3.5-turbo-0613 and gpt-3.5-turbo-16k-0613 models (langgenius#8500) feat: Add ComfyUI tool for Stable Diffusion (langgenius#8160) chore: update the .gitignore file to include opensearch,pgvector,and myscale (langgenius#8470) feat: Add base URL settings and secure_ascii options to the Brave search tool (langgenius#8463) feat: add flux dev of siliconflow image-gen tool (langgenius#8450) chore: workflow BRANCH, PARALLEL i18n (langgenius#8452) ... # Conflicts: # api/core/file/file_obj.py # api/core/file/message_file_parser.py # api/core/helper/code_executor/code_executor.py # api/core/workflow/nodes/code/code_node.py # api/core/workflow/nodes/tool/tool_node.py
@wisepmlin This seems to be a network issue. I have tried to install Mac comflowy and it worked too. |
https://docs.dify.ai/tutorials/tool-configuration/comfyui 的链接无法访问 |
@Dongnc1017 The comments above have already mentioned it. You should download those models which contain text encoders, then put them into Flux Dev and Flux Schnell are both supported. |
Hi @QunBB, would you be interested in updating the documentation for this tool? Or perhaps removing the inaccessible links from the configuration? |
@laipz8200 I'm intersted in updating it when i'm free later. I would replace the current link with the official ComfyUI website first, and will add it again when i finish the documentation in dify. |
Hi @QunBB I think current ComfyUI tool can be better by reduce the user input and selection, just give the user a The comfyUi workflow is similar to dify's workflow, support a variety of nodes. Current implementation seems define specific steps, the user can only select each params of these steps, seems inflexible. A more reasonable user case is: the user edit the workflow in the comfy UI, and then export the json of this workflow which is simliar to dify's DSL, then paste it to this tool to get the image in dify. Now they combine the dify and comfyUI's workflow. This is the export API button: This is a simple workflow just to change an ICON's style, but it has 40 nodes, current solution can't do this: what do you guys think about this ? |
@hjlarry Sure, we could add it, then it will support any image generation workflows in ComfyUI. But i don't think LLM could correctly generate the prompt text via agent, so it may only be used in dify's workflow. |
@QunBB Sure, we can add a new tool and keep both of them. |
@hjlarry It is a good idea. |
Checklist:
Important
Please review the checklist below before submitting your pull request.
dev/reformat
(backend) andcd web && npx lint-staged
(frontend) to appease the lint godsDescription
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue. Close issue syntax:
Fixes #<issue number>
, see documentation for more details.Fixes
Type of Change
Testing Instructions
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration