EditUtils: Boogu Model Config lrzjason

BooguModelConfig_EditUtils is the smallest node in the Boogu branch of this pack, and it exists to do one thing: hand the encode pipeline a dictionary that says "we are editing with Boogu, here's how to treat its images." One optional instruction input, one model_config output - that's the whole interface.

The dictionary it produces is tiny: model_name: "boogu", vae_unit: 8, and an empty llama_template. Each field matters in its own boring way. model_name is the routing key that makes EditTextEncode_EditUtils take the Boogu code path instead of the Qwen/Flux2Klein one. vae_unit: 8 tells it to align everything to multiples of 8, Boogu's VAE spatial unit, so the padding math stays clean. And llama_template being empty is a quiet design decision worth knowing: Boogu's tokenizer picks its own system prompt, so unlike the Krea 2 and Qwen configs there's nothing for you to supply.

That's also why the instruction input is a bit of a troll. It's there, it's multiline, and the node ignores it. The source code is explicit about it - Boogu auto-selects the system prompt, custom instructions are dropped rather than honored. If you type a careful instruction in there expecting it to change the edit behavior, you'll be confused for a while and then annoyed. Don't be. Leave it empty.

So why does the node exist at all instead of you just typing into a text field? Because it gives the graph a typed contract. model_config is a DICT, it carries all three fields in one wire, and it's what lets you swap whole model stacks by rerouting a single connection - Boogu out, Krea 2 in, same encode node. The unified-interface design of this pack (one EditTextEncode serving four model families) only works because each family has a config node that pre-negotiates the differences.

The one gotcha that's actually worth your time: this config alone isn't a working workflow. It feeds EditTextEncode_EditUtils, which also needs a clip and vae that actually match Boogu - Boogu-Image uses a Qwen3-VL text encoder and its own VAE, and the README reminds you the model is something you bring yourself; this pack ships none of the weights. Install: ComfyUI Manager (search "EditUtils") or git clone https://github.com/lrzjason/ComfyUI-EditUtils into custom_nodes, restart. Zero dependencies beyond what ComfyUI already has.