lllyasviel / lllyasviel/stable-diffusion-webui-forge

What about an existing Comfy checkout? (webui-user.bat)

Open
#2,175 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
13k
Forks
1.7k
PR merge metrics
No merged PRs in 30d

Description

Hello
In your webui user bat file you have prepared lines to uncomment to link to an existing a1111 installation, like this:
![image](https://github.com/user-attachments/assets/48cdaa35-5c12-4735-93fb-5c2561362163)

Ok but what about an existing ComfyUI install?

I don't want to go set paths for everything manaullay (models, vae, controlnet etc)

-> You should prepare the same comments but suited for an existing comfy installation.
-> In any case it would be way better if it was possible to configure everything in the GUI inside the settings page (https://github.com/lllyasviel/stable-diffusion-webui-forge/issues/2174)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with webui-user.bat and review the related GUI-settings discussion in issue #2174. Determine how an existing ComfyUI checkout should be selected and how its models, VAE, and ControlNet paths are handled. Done means users can reuse that installation without manually configuring each path.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.