Tag Data Deleter

Save enough tag collections with Tag Data Saver and the dropdowns on the Loader nodes start filling up with things you no longer need - a query you were testing, a name you typo'd, a pull that turned out mediocre. Tag Data Deleter is the cleanup half of that loop: pick a saved collection by name, run the node, and it's gone from disk.

It's a small, single-purpose node, and there isn't much more to it than that description. But it's worth its own explanation because of how it behaves inside a ComfyUI graph specifically, which is a little different from what you'd expect from a "delete" action in most other software.

What it's for, concretely

Over time, if you're actually using LPP's save/load loop the way it's designed - locking in good queries as named collections and reloading them instead of re-querying - that list of saved names grows. Old test collections, one-off experiments, a Derpibooru pull you saved before realizing the filter was wrong: none of that gets cleaned up automatically, and a cluttered dropdown makes the good collections harder to find in the noise. This node exists purely so that list doesn't just grow forever.

The inputs and outputs that matter

• collection_name - an enum dropdown, the same style as the Loader nodes: it lists whatever collections you've saved. If nothing's been saved yet, it's empty, which is expected rather than broken.

There are no outputs. Like the Saver, this is a terminal, is_output_node: true action node - it doesn't produce anything for the rest of your graph to use. Its entire job is the side effect of removing a saved collection.

How to install it

It's bundled with the rest of the Lazy Pony Prompter pack - no separate install. Via ComfyUI Manager: search "Lazy Pony Prompter," install, restart. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/Siberpone/lazy-pony-prompter

Restart ComfyUI afterward. Nothing heavy comes with it - no model downloads, no extra dependencies. It sits under the top-level LPP category, same as the Saver, since it isn't tied to a specific booru.

Common issues & troubleshooting

Deleted the wrong thing, or lost more than expected. There's no confirmation dialog here - this is a straightforward file-delete action node, not a "move to trash" with an undo. Double-check collection_name before you queue a graph containing this node, especially if you've got several similarly-named collections from testing different queries.

It fires when you didn't mean it to. Because this is an output node, ComfyUI executes it whenever it's part of the active graph on a queue run - which means if you leave it permanently wired into a workflow you also use for actual generation, it can delete on runs where deletion wasn't the point of queuing at all. The safe pattern is to only connect it when you actually intend to delete something, then disconnect or bypass it right after - don't leave it live in a pipeline you queue routinely.

Dropdown is empty. Nothing's been saved yet, or everything that was saved has already been deleted. Not a bug - there's simply nothing to list.

Deleted a collection you still needed elsewhere. Deleting here removes it for every Loader node of that booru type - a Danbooru collection deleted here won't show up in the Danbooru Loader's dropdown anymore. If you're sharing a small set of curated collections across multiple workflows, be sure nothing else still depends on the one you're about to remove.

General roughness. The README notes the ComfyUI nodes in this pack are "somewhat experimental and may have some bugs," with interface compromises made to work within ComfyUI. Treat minor friction as a known tradeoff rather than something you misconfigured.