Boyo LoRA Config Inspector

The pack's LoRA system lives or dies on its JSON config files - and config files, being hand-edit-able JSON, go stale. A prompt gets a typo, a LoRA gets renamed, a path breaks, and suddenly your Paired Loader silently feeds nothing into the model. Boyo LoRA Config Inspector is the pre-flight check: pick a config and it reads the file, formats a human-readable breakdown, verifies whether the referenced LoRA files actually exist, and hands you the raw JSON. Connect it before your loader and debug with your eyes instead of the sampler's silent failure.

The inputs

• config_to_inspect - dropdown of configs in the pack's lora_configs folder. Pick the one you're about to load.
• refresh_trigger - optional INT. The tooltip says it plainly: change this value to refresh the config list when you've added new files without restarting.

Outputs (all STRING):

• config_summary - the readable breakdown: config type, prompts, and what the inspector found.
• raw_json - the unmodified JSON contents.
• file_status - which referenced LoRA files exist and which are missing. This is the one you want to see all-green before hitting run.

Install

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

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

Restart. No extra dependencies.

How to actually use it

Drop it in the graph alongside (not instead of) your loader - it's an output node, so it can sit on its own branch and just report. If file_status flags a missing LoRA, you've caught the problem before generation: rebuild the config with Boyo LoRA JSON Builder or fix the file name. If the summary shows prompts you don't remember writing, the config's been edited by hand and you know where to look. Ten seconds of inspection beats a 400-frame render that comes out as if no LoRA was ever applied.