lllyasviel / lllyasviel/stable-diffusion-webui-forge
[Feature Request]: A feature to save all settings, including ones used in integrated extensions
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
### Is there an existing issue for this?
- [X] I have searched the existing issues and checked the recent builds/commits
### What would your feature do ?
Basically I propose a feature or setting similar to [this](https://github.com/ilian6806/stable-diffusion-webui-state), or maybe implement that exact extension.
Would be beneficial to have this given all the different extension integrations Forge comes with. The aforementioned extension saves settings from adetailer, dyn prompt, multidiffusion, and another, but it cannot restore anything past those. Similarly, sending the metadata from an image also does not affect the integrated plugins.
### Proposed workflow
1. Open webui
2. Begin setting up workflow and generate images
3. After session is over, click a button that will record all tweaked settings and send them to a json file into a directory of the user's choosing.
4. Load up webui again
5. Drag n drop/import/load json file into the ui to begin previously used workflow right away.
### Additional information
_No response_
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked stable-diffusion-webui-state extension and how Forge's integrated extensions expose their settings. Define how the UI should capture and restore settings across adetailer, dyn prompt, multidiffusion, and other integrations, then verify that a user-selected JSON file can save and reload the complete workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100