FSL / Image Memory → Clear

A boring little housekeeping node that earns its place. FSLImageMemoryClear deletes the image stored under one key from the FSL pack's in-process memory stash - the same memory that FSLImageMemoryStore writes to and FSLImageMemoryRecallSafe reads from. No inputs beyond a key, no outputs at all. It's an output node whose entire job is the side effect.

Why you need it

The memory dict is global and sticky. Whatever you store under a key stays there until something removes it, across runs and queue executions - restarting ComfyUI clears it, but nothing else does. That's the trap: in an iterative workflow, if run #3 stores a result under "last" and you go back to run #2's state, recall still hands you run #3's image because the old value never left.

So the mental model is: Store is write, Recall is read, Clear is delete-one, Clear All is drop the whole table. You typically place a Clear in one of two spots:

• At the start of a fresh run - so a stale key can't answer for the new pass. Fred's own iterative workflow keeps the clear nodes bypassed by default and un-bypasses them when you want a reset.
• At the end of a batch - hygiene, so the next project doesn't inherit leftover state.

The input

• key - the exact key to remove. Default "last". It must match the Store node's key character-for-character; _MEM.pop(key, None) won't complain if it doesn't exist, it just no-ops.

The node returns nothing. ComfyUI treats it as an output node, so it runs and prints [FSLImageMemoryClear] cleared key='...' to the console. Because it has no output sockets, ComfyUI's usual dependency model doesn't force it to run at a particular time - if ordering matters, connect it into the chain where you can, or just remember it executes on queue.

Install

It ships with the pack, so: ComfyUI Manager → "ComfyUI FSL Nodes", or clone + pip install -r requirements.txt, restart. Like its Store/Recall siblings it's pure local Python - no API key, no cloud, no cost.

Honestly, that's the whole article. If you use the FSL memory nodes at all, you'll reach for this the moment you see recall returning the wrong image. If you never use memory, you'll never touch it. Just don't confuse it with Clear All - one nukes a single key, the other wipes the whole dict, and in a busy workflow they're easy to grab interchangeably.