🌊🥗 FlowState Chef Ingredients

Every FlowState Chef workflow starts here. Chef is a two-stage editing pipeline - Qwen-Image-Edit makes the edit, Flux polishes it - but it deliberately takes none of the prompts or images directly. All of that arrives on one wire, and this node is the thing that builds it. Think of it as the grocery bag: you fill it with the edit instructions, the refinement instructions, and the pictures, and hand the whole thing to the Chef.

What it packs

Three things go in:

• qwen_edit_prompt - the actual instruction to Qwen-Image-Edit: "change the jacket to leather," "remove the car in the background," "make it raining."
• flux_refinement_prompt - what the final output should look like after the edit, described as a clean image prompt. Qwen does the work; this tells Flux what the finished plate should read as.
• image (plus optional image_2, image_3, image_4) - the starting image(s). Four images means four batch items, which is how you edit a whole product line or thumbnail series in one run.

One output: chef_ingredients, a wildcard-type object that carries the prompts and image batch into FlowState_Chef.

Why it exists

It's a packaging node, and it feels redundant until you use the Chef - which does the same staged-caching trick the rest of this suite does. The Chef tracks whether the Qwen stage or the Flux stage needs re-running, and it does that by diffing this ingredients object. Change only the refinement prompt and the Chef skips Qwen entirely; swap in a new image and both stages re-run. Because the prompts and image arrive as one structured input, that "did anything actually change?" check is cheap and reliable. The wire isn't for tidiness - it's the mechanism.

The honest take

There is nothing clever here. It's a text-boxes-and-image-inputs node whose entire job is feeding one specific downstream node, and the --- ✏️ Qwen Edit Prompt --- label fields above the boxes are explicitly non-functional labels the author ships to visually group settings. You can't use it for anything else, and you shouldn't try - it's a component, not a tool. What it buys you is a workflow that reads the way you'd describe the process out loud, and one that the Chef can cache intelligently.

Install and use

It ships in the FlowState Creator Suite, so it installs with the pack - no separate install, no extra dependencies:

cd ComfyUI/custom_nodes
git clone https://github.com/flowstateeng/FlowState-Creator-Nodes

then restart ComfyUI (or use ComfyUI Manager, search FlowState-Creator-Nodes). Wire its chef_ingredients output into the Chef's chef_ingredients input, load your image with a standard Load Image node, and write the two prompts. If you've got the Chef open without this node, you'll see an unfilled red socket and no obvious way forward - that's the moment to remember the bag exists. Only real gotcha: the edit prompt and refinement prompt get different treatment downstream, so don't put "remove the trash can" in the Flux field. Keep the instruction with Qwen and the description with Flux, or you'll get a beautiful polished version of the wrong edit.