SP_CacheManager

Every caching system eventually needs a way to look inside it and clean it out, and that's what SP_CacheManager is for: "View, clear a key, or clear the entire cache," in the pack's own words. It's the maintenance node for the whole SP_Cache family - SP_CacheAutoLoader, SP_CacheGet, SP_CacheStore, SP_CacheValue and the rest all read and write the same shared cache, and this is the node that lets you see what's in it or wipe it without restarting ComfyUI.

You'll reach for this most often after editing something upstream of a cached node and getting stale output back - the caching nodes key off a string you chose, not off a hash of their actual inputs, so nothing invalidates automatically when the real input changes. SP_CacheManager is how you fix that by hand.

How it works

The node runs a single action per execution, picked from a fixed set, and reports back what happened as text.

Inputs and outputs

• action (required, enum: view, clear_key, clear_all) - pick one. view inspects the current cache state; clear_key removes one entry; clear_all wipes everything.
• key (STRING, optional, default default_key) - only relevant when action is clear_key; ignored otherwise.
• Output: cache_info (STRING) - the result of whichever action ran, most useful with view.

Installing it

ComfyUI Manager: search "SP-Nodes", install, restart. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/bananasss00/ComfyUI-SP-Nodes

then restart ComfyUI. Nothing extra to install for this node.

Common issues

clear_key did nothing. This is a straight string match against whatever key the caching node used - a typo, different casing, or a key that was built dynamically (say, via SP_CompositeCacheKey) and doesn't match what you typed by hand will silently miss. Run view first to see the actual key strings currently stored before trying to clear one.

clear_all feels drastic, and it is. It wipes every key in the shared cache, not just the ones from the workflow you're currently looking at - if you've got multiple graphs relying on cached values from earlier runs, this takes all of them out at once. For a single stale entry, clear_key is almost always the better tool.

You keep having to clear the cache manually. If a value goes stale every time you touch an upstream setting, that's a sign the cache key itself should encode that setting - build it with SP_CompositeCacheKey out of the parts that actually determine the output, rather than relying on yourself to remember to clear it by hand each time.