[Feature Request] TRUE SAVE (saving the states of outputs).
- Dominant language
- Python
- Stars
- 133k
- Forks
- 15.7k
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 155
Description
### Feature Idea
when you run a workflow, then add an additional save image input then rerun it, comfy will naturally start running at the level of the newly added nodes (provided nothing has changed in the alreayd run workflow)
Problem is lets say my workflow produced some complicated "set of images" that are saved in multiple nodes.
If I want to add an extra node and rerun, ok everything will run as expected.
But what if I closed comfy or the pc and I wanted to replace the images wherever they were before adding that extra node.
I would not be able. EVEN IF the workflow was identical. I would need to run it again and obtain the same "set of images" obtained previously, to be able to "treat" them again with additional nodes.
What I want is a "true save" that will save the workflow WITH ITS OUTPUT.
When I run it, ONLY the "loading model/vae/etc" nodes will run, but anything in between (upscale/ adetailed/encode/decode) is not run, instead the workflow REMEMMBERS the previous output it got from its previous run of the same workflow, thought.. the save.
I can load a workflow WITH ITS outputs and continue modify it, even after reseting comfy/pc, and I can continue working on that workflow and those outputs direclty (just need to wait for the modesl to be loaded again).
Is the idea clear?
### Existing Solutions
_No response_
### Other
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.