String

Most merge weights are numbers. Some aren't. A few operations in the mecha world want a string - a component name to pick, a dtype to cast to, an identifier of some kind - and the recipe graph is built around MECHA_RECIPE objects, not raw text. The String node in comfy-mecha is the tiny adapter that lifts a string into the recipe graph so it can flow where a (param)-space recipe is expected.

Input:

• value - a STRING. Type whatever text you need.

Output:

• recipe - a MECHA_RECIPE wrapping that string.

What it's actually for

It's a hyper node - a "parameter producer," in the same family as Float, Int, and Bool - just for text. The concrete use cases are narrow: operations that take a string parameter (a component name, a dtype string, a config identifier) rather than a tensor weight. When a recipe method you're using has an input whose space is (param) and the docs say it wants a string, this is the node that converts your typing into something you can wire in.

How it works

There's no real mechanism to speak of - that's the point. The node takes the text, packages it as a literal recipe node in the param space, and hands it out. Every other node in the pack that needs a string parameter can then read it from the recipe, exactly like it would read a float from Float Mecha Hyper.

Install

Pack-level: 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 ComfyUI. Only dependency is sd-mecha; no model downloads.

Gotchas

Honestly, most merges never need this node. If you're not doing anything exotic - no custom merge methods, no string-taking recipe inputs - you can ignore it entirely. When you do hit a recipe input that expects a string and you're staring at a required text field with no obvious producer, this is the missing piece. And it only feeds (param)-space string inputs; you can't use it to label or annotate a workflow, so don't go looking for a name tag.