Deserializer

Mecha Deserializer is the load half of the pack's recipe bookkeeping. comfy-mecha can serialize any merge recipe into a human-readable text format (the .mecha format) - and this node takes that text and turns it back into a live MECHA_RECIPE. It's the inverse of the Serializer node: one produces the text, the other consumes it.

Why would you want text of a recipe at all? Because a recipe is a description of a merge, not a merged model. That description is far more portable and versionable than a checkpoint: you can save it in a workflow, paste it into a git commit or a forum post, diff two recipes, or re-run the same merge later after fixing one upstream input. The pack's author explicitly built this for bookkeeping - the original motivation was "keeping track of the things I had already tried was getting unwieldy with text files."

Inputs

• recipe_txt - a multiline STRING, default empty. Paste your .mecha text here.

Output: one recipe (MECHA_RECIPE), ready to wire into merge nodes or Mecha Merger. You can chain: build a recipe → Serializer → copy text → paste into Deserializer → identical recipe. Round-trips are the point.

Practical shape

Serializer ──▶ recipe_txt ──▶ (copy) ──▶ Deserializer ──▶ Merger

In practice: keep a few .mecha recipe snippets in a notes file as your "merge recipes library," and rebuild any of them by pasting into Deserializer. It's also how you'd share a merge recipe without shipping a full model - though note the recipe references your model files by name, so whoever loads it needs those files in the same folders.

Install & gotchas

ComfyUI Manager → search mecha → Mecha Merge Node Pack, or:

cd ComfyUI/custom_nodes
git clone https://github.com/ljleb/comfy-mecha.git
pip install -r comfy-mecha/requirements.txt

Restart; only dependency is sd-mecha==1.1.7.

The gotchas are real but specific. The text format is line-oriented - multi-line paste is expected; a one-line mangled string usually means a parse error, which the node reports clearly rather than silently corrupting. Serialized recipes reference model paths/names, so a recipe that round-trips on your machine can fail to load on someone else's until their files are in place. And this node deserializes; there's a sibling Serializer for the reverse. If you paste text and get nothing, you're probably looking at the wrong node. It's a niche tool - but when you've rebuilt a favorite merge for the fifth time, you'll be glad it exists.