Lmcq Auth Workflow Decryption

If someone sent you a workflow encrypted with LmcqAuthWorkflowEncryption, this is the node that turns it back into a normal, loadable ComfyUI JSON file. It's a small, single-purpose node - three fields, no outputs, and its only job is writing a decrypted copy of the file next to the encrypted one.

The fields. workflow_file is a dropdown listing the encrypted workflow files it can find (in your ComfyUI root workflows folder or the plugin's own workflows folder). key is the password the creator set when they encrypted it - this has to match exactly, no fuzzy matching on typos or case. save_name (default decrypted_workflow) is what the output file gets called. There's no machine_codes field here, unlike the encryption side - if the file was machine-locked at encryption time, that check happens automatically against your current hardware rather than something you type in.

What happens after decryption. This node writes a plain, unencrypted workflow JSON to disk - same folder as the source file, per the README. From there it behaves exactly like any other ComfyUI workflow: open it through the workflow menu or drag it in, same as you'd load anything you'd built yourself. The node itself has no wired outputs; it's a file-writing utility, not something that stays connected to the rest of your graph.

Why "Auth" and not "Runtime." This belongs to LMCQ's cloud-backed authentication system, as opposed to the pack's local-only Runtime workflow protection. Per the README, that means decryption can involve a live check against LMCQ's own auth server - validating machine binding, expiration, or usage limits set by the creator - rather than being a fully offline password check. Practically, that means a failed decryption here isn't always a wrong password; if the creator set an expiration or a usage cap, decryption can fail even with the correct key once that limit is hit, and there's nothing to fix on your end except asking the creator to extend it through their account on LMCQ's platform.

Installing it. Through ComfyUI Manager (search "ComfyUI-LMCQ") or manually:

cd ComfyUI/custom_nodes
git clone https://github.com/sebord/ComfyUI-LMCQ

Restart ComfyUI afterward.

The bug most people actually hit. Before troubleshooting a password, check whether the node is visible at all. ComfyUI-LMCQ's Auth and Runtime protection nodes share a compiled runtime module that's gone missing on some installs, throwing a ModuleNotFoundError (runtime.model_protection or api_model_protection) at ComfyUI startup - and because that failing import sits inside the pack's shared __init__.py, it takes down the entire pack's node registration, not just the encryption-related ones. If LmcqAuthWorkflowDecryption (or anything else with the Lmcq prefix) isn't in your node search, look at your console log for that specific error first. The pack's January 2026 changelog covers the fix directly: copy the Python-version-matching files from the runtime directory into the runtime root, delete the ones that don't match, and restart ComfyUI.

If the node is loading fine and decryption is still failing, work through the ordinary suspects in order: retype (or better, copy-paste) the password to rule out a typo, confirm the encrypted file wasn't partially transferred or corrupted, and - if you know it was machine-locked - confirm your current machine's code was actually added to the authorized list before the file was encrypted. That last one can't be worked around locally; it needs the original creator to re-encrypt with your code included.