Reload Model

Reload Model loads a model - checkpoint, CLIP and VAE - back from disk by filename, so a Cyclist loop can pick up the model it saved on the previous run. It's the read counterpart to Save Model (Override), and together they're the heaviest, most specialised pairing in the pack: they let the model itself be the thing that evolves across loop iterations.

If you landed here from a search, a quick expectation-set: this is not a general-purpose checkpoint loader. It's a loop node. If you just want to load a model normally, use ComfyUI's built-in Load Checkpoint - Reload Model is specifically for reading back a checkpoint that Save Model (Override) wrote earlier in the same iterative cycle.

What it's for

Cyclist builds loops from ComfyUI's queue - each Queue Prompt is one iteration - and the Override/Reload disk pair carries state between them. For most loops that state is an image or a latent; Reload/Save Model is for the rare loop where you're mutating a model pass after pass. The pack's example is a LoRA burn-in test: each iteration reloads the model saved last run, stacks another random LoRA onto it, and saves it again, until the model finally breaks. It's a stress test for LoRA compatibility, and it's about the only place this node makes sense.

The inputs and outputs

• filename (STRING, default ForLoop_1) - the saved model to load, matching the name Save Model (Override) wrote.
• fallback_m (MODEL, optional) - model to use when nothing's saved yet (first iteration).
• fallback_c (CLIP, optional) - CLIP fallback for the first pass.
• fallback_v (VAE, optional) - VAE fallback for the first pass.

The three fallbacks are how iteration one bootstraps: before anything's been saved, wire your normal Load Checkpoint outputs into them so the loop has a real model to start from. Outputs are MODEL, CLIP and VAE - the full set, ready to feed a sampler or another model-patching node.

Install

• ComfyUI Manager: search comfyui-cyclist, install, restart.
• Manual: cd ComfyUI/custom_nodes && git clone https://github.com/Pos13/comfyui-cyclist, restart.

Pure Python - but the files it moves are anything but light.

What to watch

Checkpoints are multi-gigabyte, so every iteration reloads a full model from disk - that's slow and I/O-heavy. This is not a node for a tight, fast loop; only use it when persisting the whole model between passes is genuinely the point. Wire your fallbacks so the first iteration doesn't come up empty, and expect each pass to spend real time on the load/save round trip.

The pack's "New Cycle" rule applies (only filename widgets and Primitives auto-increment, not Recall String / String Const names), and Cyclist as a whole is archived and unmaintained. Given this node handles large model files, test a save-and-reload round trip on your setup before building anything long on it.