Anymatix Model Patch Loader

Model patches are the quiet middle-child of the ComfyUI loader family: a file of patch tensors that gets layered onto a diffusion model by an Apply node, rather than a full model you sample with directly. AnymatixModelPatchLoader is the Anymatix-pack twin of ComfyUI's own ModelPatchLoader - same job, same output type, one difference: it takes a string path instead of a dropdown.

If you've never used the stock node, you can still read this one in a sentence: give it the name of a model-patch file, and it returns a MODEL_PATCH object that a corresponding apply-patch node can fuse onto your model. It inherits directly from ComfyUI's ModelPatchLoader and overrides nothing except the input mechanism - strip the path to its basename, then call the parent's loader. That's the whole difference, and it's exactly the difference every loader in this pack exists to make.

Why a string instead of a dropdown

This is the pack's core design and it's worth understanding once, because it applies to every loader in it. Anymatix - the desktop app this pack serves - addresses models by URL rather than filename. A workflow says "this patch, this checkpoint," and a fetcher node downloads the file on demand, verifies its size and hash, deduplicates it, and hands a loader a local path. The path points at a file that may not have existed when the workflow was authored, which is precisely why the loader can't use ComfyUI's normal dropdown-of-existing-files. The dropdown only knows what's on disk at graph-build time; a URL fetcher knows what the file should be. So the loader's contract is: accept the path, resolve the basename, load.

Inputs and output

• name (STRING) - full path to the model patch file, straight from a fetcher node or typed by hand. The loader strips it to the basename and resolves it against your model_patches folder (or wherever extra_model_paths.yaml points it).

Output: MODEL_PATCH - feed it to the apply node that matches the patch type (the generic ModelPatchApply-style consumers that ComfyUI's own ModelPatchLoader feeds). What the patch actually does depends entirely on the file: some patches are architectural tweaks, some are task adapters. This node doesn't care; it just gets the tensors in memory.

Install

In the menu it sits under "Anymatix", shipped by the anymatix-comfy-nodes pack. ComfyUI Manager: search "anymatix-comfy-nodes" and install, then restart. Or:

cd ComfyUI/custom_nodes
git clone https://github.com/Anymatix/anymatix-comfy-nodes

then restart ComfyUI. You do not need the Anymatix app to use any of this - the README is explicit that the pack is published so Anymatix-exported workflows open in stock ComfyUI.

Gotchas

Because the loader resolves by basename, a patch file with a duplicate name in another model folder will confuse it - keep patch filenames unique, the same rule as every ComfyUI loader. And if you hand it a file that hasn't been downloaded yet (no fetcher in front of it, file missing on disk), you'll get a not-found error rather than a silent skip; that's ComfyUI's own behaviour surfacing, and the fix is to let the fetcher run first.