Text Decrypt 🔒

This is the other half of TextEncrypt, and it's a one-job node: feed it ciphertext, get back the plain string. The pack's own description for it is specific about the direction - it decrypts text that was encrypted with the client's public key, unlocked here using the server's private key, the same keypair the server auto-generates on startup as part of CryptIO's whole "no manual key management" design.

If you landed here searching for a node that encrypts a workflow or a model file so nobody else can open it, this isn't it - that's a different category of node entirely (LmcqAuthWorkflowDecryption and similar are built for that). TextDecrypt is about text that got scrambled crossing the network between a browser and a ComfyUI server, not about protecting intellectual property.

The one input, the one output

There's a single required field, encrypted_text - a multiline string whose default placeholder is literally ENCRYPTED:.... That prefix is a hint about the expected shape: this field wants a real ciphertext string, produced by the matching encryption step (a TextEncrypt node elsewhere in the graph, or whatever else in the pack generated it), not arbitrary typed text. Feed it something that was never actually encrypted and don't expect a clean result.

The output is decrypted_text - a plain STRING you can wire into anything downstream that wants readable text: a CLIP Text Encode, a save node, a display widget, whatever the rest of your graph needs.

Where it fits in the wider picture

CryptIO exists because ComfyUI, by default, has no authentication on its API and no encryption on its traffic - a gap the community has flagged loudly enough that "secure your instance" is a recurring PSA topic in the ecosystem. If you're running workflows on a remote or shared machine rather than your own local box, that's the exact situation where a plain string crossing the wire in the clear is a real (if narrow) exposure. TextEncrypt/TextDecrypt give you a way to keep a specific piece of text opaque in transit without hand-rolling any crypto yourself - the browser does the RSA encryption automatically once it's fetched the server's public key, and this node does the corresponding unlock server-side.

Installing it

Same install as every node in this pack, since it's all one repo: ComfyUI Manager, search "ComfyUI-CryptIO," install, restart - or manually cd ComfyUI/custom_nodes && git clone https://github.com/Suzu008/ComfyUI-CryptIO and restart. No models, no heavyweight dependencies to wait on; it's a small Python + frontend-JS pack.

Troubleshooting

The failure mode to expect is a decrypt error when the input isn't genuine ciphertext - if you paste plain text into encrypted_text, or if it got truncated or mangled somewhere upstream (copy-pasted through something that reformats whitespace, for instance), decryption will fail rather than silently returning garbage back as "decrypted" text.

Also worth flagging honestly: this is a small, recently-scaffolded pack - the README still shows the unedited boilerplate from ComfyUI's official cookiecutter extension template, and there's essentially no community track record to lean on yet (no forum threads, no install-base signal). Treat it as a useful, narrowly-scoped utility rather than a hardened security product, and if a decrypt call fails on you, the first thing to check is simply whether the text you're feeding it actually came out of the matching encrypt step in the same session - the server generates a fresh keypair per startup, so ciphertext from a previous server run won't decrypt against a new one.