Language Package Manager

Here's the thing nobody warns you about with this pack: the first time you translate any language pair, the node downloads that pair's translation model on the spot, and ComfyUI sits there frozen until it's done. Language Package Manager is the pack's answer to that - a node that lets you check and install those models ahead of time, so the actual translation later is instant and offline.

The engine here is Argos Translate, which ships no models at all. Every language pair is a separate neural model (OpenNMT, running on CTranslate2) that gets fetched from Argos' package index and installed into its local store the first time you ask for it. This node just gives you a handle on that process: check whether a pair is installed, or install it, without needing a translation to happen first.

How it works

You pick a source_language and a target_language, pick an action of check or install, and queue the graph once. It returns a status string telling you what happened.

• check (default) - looks in the installed-package store and reports whether the pair is ready, whether the languages exist but no model covers the pair, or whether it's simply not installed.
• install - downloads and installs the model for that pair right now. Same download the translator would trigger lazily, just on your schedule.

Output is a single STRING (status) with a human-readable message like Package it->en is installed and ready. Read it from a text display node, or just watch the console.

The inputs that matter

• source_language and target_language - no "auto" here; you must pick two concrete languages (the defaults are it - Italian and en - English, which tells you a lot about who wrote this pack).
• action - check or install.

Installing it

Standard for the pack. ComfyUI Manager, search ComfyUI-Prompt-Translator, install, restart:

cd ComfyUI/custom_nodes
git clone https://github.com/DrStone71/ComfyUI-Prompt-Translator

Restart, and if imports fail run pip install -r requirements.txt inside the cloned folder - argostranslate and ctranslate2 are the ones that matter here. It's under 🌐 DrStone71.

Why you'd bother

If you only ever translate one pair (say, your own language → English), you honestly don't need this node - just accept the one slow first run. It earns its keep once you translate several pairs, or when you're setting up a machine to run offline, or when you want to pre-warm models before a big batch instead of freezing mid-run. The packs are each tens of megabytes and stored per-pair on disk, so a handful of pairs is nothing. Practical routine: throw one in a throwaway graph, set it to install for the pairs you use, run it once, then delete the node - every future translation for those pairs is then instant and fully offline.