AI Prompt Dexogen External

If you've used ComfyUI-Pixaroma's AI Prompt node, you know the workflow: a saved formula on the node, an idea, an optional wired-in text, and a clean prompt out the other end. AI Prompt Dexogen External is that same loop, except it doesn't ship with a built-in LLM or demand a subscription. You point it at any OpenAI-compatible endpoint - Ollama on localhost, LM Studio, OpenRouter, vLLM, a paid API - and it just calls it.

The name is a little intimidating; the reality is friendlier. There's no vendor lock-in here at all. If you don't pick a model, the node degrades gracefully: your idea and wired text pass through untouched, so the graph still runs while you're still configuring things.

How it works

The node keeps the Pixaroma shape on the front (formula + idea + optional text + separator/order settings in its panel) and swaps the backend. When you hit generate it:

1. Joins your idea and wired text into one request,
2. Sends it to the endpoint/model you selected in the node panel,
3. Returns the model's answer as a plain STRING output.

Connect the optional image input and it encodes that image as OpenAI image content and sends it along too - but the node's own tooltip is blunt about the catch: the chosen model must advertise image input support. Wire a reference image into a text-only model and it errors, which is the "check your model supports vision" signal, not a bug.

The Danbooru presets (pony/illustrious/anima) are the interesting corner: those don't call the endpoint for tagging at all. They run a local WD SwinV2 tagger (SmilingWolf/wd-swinv2-tagger-v3) that downloads from HuggingFace on first use and feeds the model a tag suggestion plus a strict b0oru-style output policy. That's why the pack's requirements are just huggingface-hub and timm - the tagger is the only heavy thing, and it only appears if you use a preset that needs it.

The inputs and outputs that matter

This is a thin node, and that's the point. Everything else lives in its panel:

• image (optional) - reference image for a vision-capable model.
• text (optional) - wired text, joined with the idea per your order/separator settings.
• text output - the answer as a plain STRING, ready to plug into any positive-prompt input.

The one thing beginners fumble: the API key is optional, and when you do add one it's stored outside the workflow - in the OS keychain (or a local vault) behind an opaque per-node reference, not in the workflow JSON. That's genuinely good practice for a category with a real malware history - the ComfyUI_LLMVISION "LLM vision" node shipped credential-stealing code and ended in a federal prosecution (r/comfyui PSA) - and it means your key doesn't leak every time you share a workflow. The trade-off is that keys are per-machine: copy the workflow to another box and you re-enter the key there.

Install

Via ComfyUI Manager (search ComfyUI-Dexogen), or manually:

cd /path/to/ComfyUI/custom_nodes
git clone https://github.com/dexogen/ComfyUI-Dexogen.git
python -m pip install -r ComfyUI-Dexogen/requirements.txt

Restart ComfyUI and look under 🧬 Dexogen → 💬 Prompt & Text.

Gotchas

• No model selected = passthrough. The output just echoes your idea/text minus the formula. Configure the endpoint before you blame the node.
• The endpoint must actually be OpenAI-compatible. If you point it at something that isn't, you'll get transport errors rather than a prompt. Local endpoints (Ollama/LM Studio) usually need no key at all.
• First run of a Danbooru preset downloads the tagger (~hundreds of MB of SwinV2 weights). It's one-time, but it's not instant.
• The endpoint is your filter now. Whatever the model refuses, the node refuses - this is the standard trade-off of any API-backed prompt node, and it's why local models stay the community default for content the hosted path won't touch.