Boyo LoRA JSON Builder

Everything else in the pack's LoRA toolset - Paired Loader, Config Processor, Path Forwarder - runs off config files: small JSON documents that bundle a LoRA pair and their prompts into one reusable unit. Boyo LoRA JSON Builder is how you create those files without touching a text editor. Give it a name, pick the LoRAs from dropdowns, paste the prompts, and it writes the JSON into the pack's lora_configs folder where every other Boyo LoRA node will find it.

The config format is simple and worth understanding: a name, an optional high_noise_path, an optional low_noise_path, and a list of prompts. The high/low noise pair is the pack's core idea - two LoRAs, one aimed at the high-noise (early, compositional) phase of sampling and one at the low-noise (late, detail) phase. Not every config needs both; the builder even calls a config with neither a "utility config," which is a nice acknowledgment that lightning/turbo LoRAs often don't want prompts attached at all.

The inputs

• name - config name, default my_lora_config. Becomes the JSON filename.
• prompts - one prompt per line. This is where trigger words and per-LoRA context live.
• high_noise_lora / low_noise_lora - dropdowns of your models/loras folder. Pick None for a slot you don't need.
• save_config - false by default, which only previews the config in the status string. Flip it true to actually write the file.

Outputs: status (STRING - what got built, whether it saved) and config_path (STRING - where the JSON landed, empty if you didn't save).

Install

Part of Boyonodes. ComfyUI Manager → search "Boyonodes", or:

cd ComfyUI/custom_nodes
git clone https://github.com/DragonDiffusionbyBoyo/Boyonodes

Restart. No extra dependencies beyond the pack itself.

Gotchas

The default save_config state is false, so it's easy to "build" a config and walk away without a file on disk - if config_path comes back empty, that's why. Configs save into custom_nodes/Boyonodes/lora_configs/ and the reader nodes expect them there. And the LoRA paths are stored relative to models/loras/, so if you move a LoRA file to another folder, existing configs will silently point at nothing until you rebuild them.