Workflows
The Workflows page is the library Remix runs from: every workflow saved in your ComfyUI, with a switch for whether the app offers it.
The library
WorkflowRemix reads the workflows folder of the ComfyUI you pointed it at. Nothing is copied or renamed. For each workflow you can:
- Switch it on, so it appears in Remix's drop-down.
- Give it a label, the name it goes by in the app.
- Open it on the inspect page with no file behind it, to see and edit its form.
- Correct its roles with ⚙ roles (below).
Those choices are kept by the app, beside your other settings. Your workflow files are left as they are.
The app runs ComfyUI's copy
A run always uses the workflow file in your ComfyUI folder as it is now. Edit a workflow in ComfyUI and save it, and the next remix uses the new version.
How a form is made
There is nothing to map by hand. The app reads the graph, asks ComfyUI what each node's settings are, and decides which are worth a control and what kind: a prompt box, a seed, a slider, a model picker, a LoRA stack, an image picker. It follows the wiring, so it knows which settings can reach the output and offers only those.
Three things it also works out:
- Muted and bypassed nodes. Their settings are listed as asleep in the hidden fields, and stay available: a style preset may wake them.
- Optional image inputs. A bypassed image loader that feeds the render is offered as an empty picker. Choosing an image switches its branch on for that run.
- Edit-instruction workflows. A workflow can declare that its prompt is an instruction for the image going in (“make the jacket red”) and not a description. Such a workflow keeps its own prompt when you switch to it.
Correcting it
Detection is usually right, and when it is not, three controls change the answer for good.
| Control | Use it when | Writes |
|---|---|---|
| ⚙ roles | The wrong field was taken for the prompt, seed, steps or guidance. | The app's settings. |
| Save field setup | You want different fields shown, or different names on them. | The app's settings. |
| ✏️ Update workflow | You want the values on screen to be the workflow's new defaults. | The workflow's own .json, after a one-time .bak. |
Only the values a run would have set are written. The rest of the graph is left exactly as it was.
A workflow from a file
Any file that carries a workflow can give it back: the workflow inside it can be saved into your ComfyUI workflows folder as a new one, and then switched on like any other. If the app recognises a file's workflow as one that is in your ComfyUI but not switched on, it says so and offers to add it.
Starter workflows
A new install copies a handful of example workflows into your ComfyUI workflows folder and switches them on. They are a starting point: they name custom nodes and models you may need to install or swap for your own. The starter workflows lists what each one does and needs.