YAML File Loader

YAML File Loader is the file-based sibling of YAML Data: instead of pasting YAML into a node, you pick a .yaml or .yml file from a dropdown and get the parsed dict out as a PYDICT. Same safe_load under the hood, same downstream consumers - but it changes how you work, because your config lives in a real file you can version and reuse across workflows.

The gotcha that will bite you first: the dropdown doesn't look in ComfyUI's input folder where you'd expect it to. It lists .yaml/.yml files in the pack's own directory - ComfyUI/custom_nodes/ComfyUI-Chaser-nodes/. The author's loader does os.listdir() on the folder containing the node's code. So the workflow is: drop your config file there, restart ComfyUI, and it appears in the yaml_file dropdown.

That also explains why the dropdown might look empty: the pack ships with zero YAML files of its own (the catalog shows 0 choices), and the file list is computed once when the node class loads. Add a file while ComfyUI is running and it won't show until you restart.

# your YAML lives here, not in ComfyUI/input/
cp my-config.yaml ComfyUI/custom_nodes/ComfyUI-Chaser-nodes/

Why bother with a file at all. If you run the same base config across many workflows - a shared set of character data, style parameters, or a prompt dictionary you tweak between sessions - keeping it in one file beats maintaining identical YAML blocks in every workflow. Edit the file, rerun, done. It also plays well with the pack's template system: the parsed PYDICT feeds Prompt Template's data input, so file-backed config drives file-backed prompts.

Worth noting:

• One file, one dict. If you want multiple named configs, use several files or nest them under keys in one file.
• The dropdown sorts alphabetically, so prefix files to control ordering if you have many.
• Updating the pack via git pull won't delete untracked files you dropped in there, but a clean re-clone will. Keep your configs somewhere versioned outside the folder and copy them back in.

Install is the standard one for this pack (Chaser's Custom Nodes by chaserhkj). ComfyUI Manager, or:

cd ComfyUI/custom_nodes
git clone https://github.com/chaserhkj/ComfyUI-Chaser-nodes

then restart. No models; the pack's dependencies (jinja2, pyyaml, requests, sexpdata, av) install automatically. And remember the author's framing - these are personal ad-hoc nodes "not meant to be used out of any context that I am already using them in," so treat the file-location behavior as a quirk to work around, not a bug to report.