🔶 Cache Reloader Any-> Save

This is the write half of Chaosaiart's frame-to-frame memory trick, and it only makes sense paired with chaosaiart_reloadAny_Load. ComfyUI graphs can't cycle back on themselves, so this pack fakes persistence across separate workflow executions instead: this node stashes a value at the end of one run, and the matching Load node hands it back at the start of the next one. That's how "frame 2 uses frame 1's output" works despite there being no literal loop in the graph - it's two runs of the same workflow, with a save in between.

It's marked as an output node, meaning it actually executes as a terminal step in the graph rather than just passing data through silently - ComfyUI will run it (and persist whatever you fed it) even if nothing downstream consumes its outputs, which is the point: the save has to happen every single run for the chain to keep working.

The fields: Any accepts literally anything (type *) - a latent, an image, a number, a whole model, doesn't matter. reloader is the slot number, 0–100, and it has to match the number set on the chaosaiart_reloadAny_Load node you're pairing it with. If you're running more than one Save/Load pair in the same workflow - say one caching a latent and another caching a running seed - give each pair a distinct number, because they all share the same slot space.

Outputs: ANY, a straight passthrough of whatever you fed in (handy for continuing to use the value downstream in the same run without a second wire back to your source), and Info, a text readout confirming what got saved.

Install path is identical across the whole pack. ComfyUI Manager: search "Chaosaiart-Nodes" and install, or use "Install via Git URL" with https://github.com/chaosaiart/Chaosaiart-Nodes. By hand: cd ComfyUI/custom_nodes && git clone https://github.com/chaosaiart/Chaosaiart-Nodes, restart ComfyUI. Linux additionally needs pip install opencv-python and pip install tqdm inside your venv - Windows gets this handled by the pack's install script, Linux doesn't.

The gotcha that trips people up most: this node has to actually run every pass for the caching to work, which means it can't sit downstream of something that only conditionally executes. And because it's tied to a reloader slot number rather than a name, a typo or a copy-pasted node with the wrong number silently breaks the chain - you won't get an error, you'll just get a Load node that keeps returning its fallback value forever, which looks exactly like "my animation isn't animating" until you go check the numbers on both ends match.