VELVET VICE KREA — Mode Selector

The "VELVET VICE KREA - Mode Selector" is the steering wheel of the whole Velvet Vice Krea 2 workflow. It's a single dropdown with four options - CREATE, NATIVE EDIT - ORIGINAL, NATIVE EDIT - CUSTOM, CLASSIC IMG2IMG - and the choice you make there ripples through the entire graph. Everything from which diffusion model loads to which preview nodes fire is downstream of this one widget. If your Velvet Vice run is producing the wrong thing, this is the first place to look.

Why one node runs the whole show

The Krea 2 Vision Prompter workflow is built around a "select your mode, only that branch executes" architecture - the same pattern the official Krea 2 ComfyUI release established with its bypass-group approach, taken further by making it data-driven. The Mode Selector is the single source of truth for that. It broadcasts a custom VELVET_VICE_KREA_MODE type across the graph, and the lazy nodes downstream (Image Router, Prompt-First Gate, the refinement previews) consult it to decide what to pull and what to leave unrendered.

It also derives two derived values you don't have to compute yourself:

prompt_profile - maps your mode onto the prompt engine's profile. Both Native Edit modes map to NATIVE EDIT, while CREATE and CLASSIC IMG2IMG keep their own names. This is what tells the Prompt Director which system prompt to use.
active_branch - a string version of the mode, for logging or driving UI state.

Inputs and outputs

One input, three outputs:

workflow_mode - the enum dropdown. CREATE, both Native Edit variants, or Classic Img2Img. That's the whole UI.
workflow_mode (output) - the same value as a VELVET_VICE_KREA_MODE wire, fed to every mode-aware node.
prompt_profile - STRING, the profile name for the Prompt Director.
active_branch - STRING, the mode name for display or logic.

There are no sliders, no hidden settings. That's deliberate - the node's job is to be boring and unambiguous so everything else in the graph can trust it.

The "only enable one branch" rule

The workflow README is blunt about this: only enable the branch you're running, and keep the other Fast Groups Bypasser groups bypassed. The Mode Selector picks which branch is active, but the lazy inputs are what prevent the others from actually rendering. If you've got multiple branches un-bypassed anyway, you'll render redundant passes regardless of what the dropdown says - the selector can't save you from a graph you've already un-muted. Get in the habit of bypassing everything except the mode you're working on, and let the selector route within that.

Installing

Standard pack install - it's one of the thirteen nodes in velvet-vice-krea:

cd ComfyUI/custom_nodes
git clone https://github.com/Velvet-Vice/velvet-vice-krea

Restart ComfyUI, or use ComfyUI Manager and search "VELVET VICE - KREA". No pip dependencies, no models to fetch.

Troubleshooting

If your prompt profile looks wrong, check whether you picked the right Native Edit variant - both map to the NATIVE EDIT profile, which is correct, but it can surprise you the first time. If the Mode Selector shows one mode and the output looks like another, the workflow_mode wire is probably crossing branches somewhere; since this custom type is shared pack-wide, ComfyUI will refuse to connect it to the wrong socket, which actually makes mis-wiring hard. And remember the node itself does zero rendering - it's pure signal. If you set CREATE and nothing renders, the problem is downstream, not here.