Remove Custom Kontext Preset 🦉| OwlV

Remove Custom Kontext Preset 🦉| OwlV is the delete key for the Owlv pack's preset store: it removes a preset you added from user_kontext_presets.json, the same file that feeds KontextTextEncode's dropdown. It's the natural pair to the pack's Add Custom Kontext Preset node, and it's just as small.

What it does

One input, two outputs. preset_name is a dropdown populated from your user presets - the ones you've added, not the ~20 built-in ones. Run it and the preset is gone, with the usual success (BOOLEAN) and log (STRING) outputs telling you what happened. Removed successfully, or "not found" if the name doesn't exist in the store.

Two things worth noting:

• Built-ins are protected. You can only remove presets that were added to the user store. The pack's own UI enforces this too - the Remove dialog inside KontextTextEncode greys out default presets and labels them "Unremovable." So you can't accidentally delete Scene Telesport, which is probably the right call.
• It shares the store, so the effect is immediate and shared. Delete a preset here and it disappears from KontextTextEncode's dropdown too, because they read the same JSON file. If a workflow still has that preset selected, the encode node will fail with "Unknown Kontext preset" - that's the one footgun to remember.

Like its Add sibling, the node never caches (IS_CHANGED returns NaN), so it always executes when you run it. If you queue it with an empty preset list, the dropdown just offers an empty string and the removal reports "not found," which is harmless.

Do you need it?

Honestly, only sometimes. KontextTextEncode has an inline Remove Custom Preset button that does the same job through the pack's /owlv/kontext_presets/remove API - nicer, with a dialog showing you exactly what's removable. The standalone node earns its place when you want removal as an explicit graph step: scripted cleanup of a preset after a batch, or managing presets before you've even added KontextTextEncode to a workflow. Its success/log outputs let you wire the outcome somewhere, which a button can't.

Install and caveats

Same pack, same install - ComfyUI Manager (search "ComfyUI-Owlv_Nodes" or "OwlV") or:

cd ComfyUI/custom_nodes
git clone https://github.com/OwlvChirotha/ComfyUI-Owlv_Nodes.git

Restart and it's under conditioning. No extra dependencies, no models. The usual small-pack caveats apply: it's a one-person project with no community support base, and because user_kontext_presets.json lives inside the pack's folder, an update or reinstall can touch your presets - keep a copy of that file if your collection matters. Remove is a one-shot action with no undo, so double-check the dropdown before you queue it.