Comfy-Org / Comfy-Org/ComfyUI

[Feautre request] Generic option for making pass through from inputs to outputs

Open
#7,879 0 comments 0 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

Hi, while new reroutes are great, I still see some option to make workflows more tidy and informative. This could be optional inputs pass through, so every input can be also available as an output on any node without actual node code modification. This might be related to https://github.com/comfyanonymous/ComfyUI/issues/511. Actually, 511 could be the subset of this one, if we consider that widget value can be taken from input. So currently there is right-click menu on the input circle allowing to set different input label. There could be also an option like "add pass through", then new output, just copying the value from the input, should appear on the right hand side. Each output that is pass through should be marked with some prefix/suffix/special character like "->" equivalent, so we can distinguish it from the original output. I prefer marking each output like this instead of creating the "pass through outputs block" for all pass through outputs, because maybe in the future there will be an option to sort inputs/outputs in arbitrary order (to avoid routing paths crossing and make view tidy even more). If input has the pass through output counter part, right click menu both fort the input and fort the output should have another option like "remove pass through". Muting the node: it's hard to tell if such outputs should be by design muted or not when the node is muted, so let's have another option in the node context menu: "Mute affects pass through" (yes/no, default=no).
Example use case:
- working a lot with masks and images - very often I need to see what is the image / mask I'm going to use or I want to see what image/mask was actually used in the node (because mask might be generated in some common/distant part of the graph). Then creating forks before the node just to have a preview of the image before the the node is making the graph untidy and also is not indicating what was used in the node as clear as "pass through" would (for example, after a node that is using mask, with new option I could make preview of the mask that was actually used in the node, and from this preview, again, adding input as a pass through output, I can use the same mask without another forking)(actually, same applies to various texts and numbers being passed around, using chained samplers with selective steps range or in img2img scenarios and many more)

### Existing Solutions

_No response_

### Other

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.