🔮 Oracle's Override

The name sounds like something that should summon a higher power. It doesn't. Oracle's Override is the most boring node in ComfyUI-Violet-Tools, and that's exactly why you want it: it's a plain manual text box that, when switched on, tells the pack's encoder to ignore everything else you've dialed in and use only what you typed.

Here's the situation it solves. You've built the full Violet prompt stack - Quality Queen feeding Scene Seductress feeding Aesthetic Alchemist - and it's spitting out prose you mostly like, but you want to A/B it against one raw prompt you typed yourself. Without this node you'd be deleting nodes or muting them one by one. With it, you flip one toggle, paste your test prompt, and the whole assembled prompt is bypassed for that run. When you're done, flip it back off and your curated stack is intact again.

How it works

Oracle's Override doesn't call an API, needs no key, and doesn't touch the sampler. It's pure text assembly. The override_prompts toggle is the switch: when it's on, the node outputs your override string (after resolving wildcards and deduping) and 🧬 Encoding Enchantress uses that text as the entire positive prompt. When it's off, the node outputs nothing and Encoding Enchantress goes back to using all the other Violet inputs normally. There's no partial blend - it's all or nothing, which is what "override" means here.

The optional chain input just prepends text to whatever's in the field, joined with a comma. It's the same additive chaining that all the pack's prompt nodes support in 2.3.0, so you can feed another node's output in front of your manual text.

The fields that matter

Only three inputs exist, and you'll mostly touch two:

• override - your multiline positive prompt. This is the whole show.
• override_prompts - the on/off switch described above. Off by default, which means the node does nothing until you want it to.
• chain (optional) - text prepended to override. Wildcards work here too.

The single output, override (an OVERRIDE_STRING), wires into the override input on Encoding Enchantress. That's the supported path - these pack-typed strings are built to plug into the pack's own conditioning hub, not a stock CLIP Text Encode node.

One nice touch: both the override and chain fields support the pack's {a|b|c} wildcard syntax, resolved repeatedly until stable. So you can keep a template like {cyberpunk city|misty forest} at {night|golden hour} and get a different run each time while still bypassing the dropdown stack.

Installing it

Oracle's Override ships with ComfyUI-Violet-Tools, so install the pack once and you get all the nodes. Easiest via ComfyUI Manager - search for Violet Tools - or manually:

cd ComfyUI/custom_nodes
git clone https://github.com/leylahviolet/ComfyUI-Violet-Tools.git

Then restart ComfyUI. The node appears under Violet Tools 💅 → Prompt. No model files to download; the only dependencies are PyYAML, rapidfuzz, and requests, and Manager installs those for you.

Where people get tripped up

The classic confusion is "I typed something and nothing changed." That's almost always the override_prompts toggle sitting at off - the node is supposed to be inert until you flip it. The second gotcha: when it's on, it replaces the whole positive prompt, so if your override text is short, the output loses all the quality boilerplate and scene detail your other nodes were contributing. That's not a bug; it's the semantics. A short override means a short prompt.

Fair warning: this is a small, niche pack with little community footprint - don't expect a wall of troubleshooting threads if something feels off. The good news is that this node is simple enough that the toggle is almost always the answer.