NS WaveSpeed Qwen Edit LoRA

Here's the odd bit of mental furniture to get used to: on this node, "LoRA" doesn't mean a .safetensors file on your disk. It means a model path on WaveSpeed's servers - the tooltip literally suggests flymy-ai/qwen-image-style-lora - that gets applied server-side to steer the edit toward a look. You're renting a style adapter, not loading one.

It's part of the Symbiotica pack's neuralsins/WaveSpeed family. The pitch makes sense once you accept the hosted frame: Qwen-Image-Edit already does instruction editing well (see the KB's inpainting doc on how it displaced mask workflows), and a LoRA sharpens the style axis on top - a consistent illustration look, a realism push, whatever the loaded adapter was trained for. You just reference it by path and set a strength.

How it works

image_url and prompt go in, the LoRA paths ride along, and the edited image returns through output_image (IMAGE). It POSTs to WaveSpeed's /api/v3/wavespeed-ai/qwen-image/edit with the LoRA params attached.

The inputs that matter:

• prompt - the edit instruction. The tooltip's example is refreshingly concrete: "Change into a white shirt and a black coat."
• image_url - source image URL.
• lora_1_path / lora_2_path - the model paths. Format is <owner>/<repo>-style, like the example. The second is optional.
• lora_1_scale / lora_2_scale - influence, 0.0 to 2.0, default 1.0. Below 1 is subtle, above 1 leans hard into the style.
• seed - -1 for random, otherwise reproducible.
• output_format - jpeg (default), png, or webp.

enable_sync_mode defaults on.

Installing

cd ComfyUI/custom_nodes
git clone https://github.com/symbiotica-ai/comfyui-nodes.git symbiotica
pip install -r symbiotica/requirements.txt

Restart or install via ComfyUI Manager (search Symbiotica). Feed an NS WaveSpeed Client with your WAVESPEED_API_KEY into client.

Common issues

• The LoRA is server-side. If you expected your local LoRA collection to be loadable here, it isn't - the path names a model WaveSpeed has on its end. Empty paths simply mean "no LoRA," so the node still works as a plain edit.
• A wrong path fails at call time. There's no local model browser to catch typos - an invalid lora_1_path errors when the API rejects it.
• Scale discipline. Two LoRAs at 1.0+ can fight each other and wash the image out. Start at 0.5–0.7 on the second one.
• URLs, not tensors. The standing rule for image_url.

The honest take: this is the node that makes the "LoRA" concept portable - same mental model as local LoRA loading, different physical location. Just remember which side of the server the weights live on.