Lmcq Runtime Workflow Decryption

If someone handed you a .lcwf file made with LmcqRuntimeWorkflowEncryption, this is the node that turns it back into a normal, loadable ComfyUI graph. Three fields, no outputs, one job: write a decrypted workflow JSON to disk so you can open it like anything else.

The fields. workflow_file is a dropdown of the encrypted .lcwf files it can find. key is the password the creator set at encryption time - has to match exactly, no partial credit for a near-miss. save_name (default decrypted_workflow) is what the output gets called. There's no machine_codes field here, and that's not an oversight - unlike the encryption side, you don't type in a machine code. If the file was locked to specific hardware, that check runs automatically against whatever machine you're actually on. Either it matches or it doesn't; there's nothing to fill in.

What happens after decryption. The node writes a plain, unencrypted workflow file to the same folder as the source .lcwf. From there it's just a normal ComfyUI workflow - open it through the workflow menu or drag it into the canvas, same as anything you built yourself. This node stays out of your actual graph entirely: no wired inputs or outputs, it's a one-shot file-writing utility, not something you leave connected downstream.

Why this side has nothing to configure. The pack's "Auth" family (LmcqAuthWorkflowDecryption) can check in with LMCQ's cloud server on decrypt - usage caps, expiration, remote revocation, all live. This "Runtime" node deliberately has none of that. It's fully offline: correct key plus authorized machine (if the file was locked to one) and it opens, no exceptions and no server that can add you after the fact if you were left off the list. That's the whole appeal of the Runtime family - nothing to depend on staying online - and also its whole limitation: a failed decrypt here has exactly one of two causes, never a lapsed subscription.

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.

Troubleshooting. First check whether the node is even visible - ComfyUI-LMCQ has a genuinely common, reported issue where a compiled runtime module the protection system depends on goes missing on some installs, throwing ModuleNotFoundError: No module named '...runtime.model_protection' at startup. Because that import lives in the pack's shared __init__.py, it silently takes down every Lmcq node, not just this one - if none of them show up in your search, check your console for that error before touching keys or machine codes. The pack's January 2026 changelog documents the fix: copy the Python-version-matching runtime files into the runtime folder, remove the ones that don't match, restart.

If the node loads but decryption fails, work the ordinary suspects first: copy-paste the key instead of retyping it, and confirm the .lcwf file wasn't corrupted or partially transferred. If both check out and it's still failing, the likely cause is a machine-code mismatch - your current machine wasn't on the authorized list when the file was encrypted. There's no local workaround for that by design; the only fix is running LmcqGetMachineCode on your machine, sending the creator that string, and getting a freshly encrypted file back. Also worth knowing if you're on a cloud or containerized setup: a machine's code depends on the underlying hardware/system fingerprint, so a file encrypted for one rented instance won't reliably decrypt on a different one tomorrow, even if it's nominally "your" machine again.