SaveModel

Calling this node "SaveModel" is the sort of naming decision that makes beginners tear their hair out, so let's clear it up immediately: it saves nothing, writes nothing to disk, and doesn't even touch a model file. If you googled it hoping for a "save my trained checkpoint" button, this isn't it. What SaveModel actually does is send a string back to Blender.

Here's the deal. SaveModel is part of ComfyUI-CUP, the bridge package that connects ComfyUI to AIGODLIKE's Blender addon, ComfyUI-BlenderAI-node. In that pipeline, ComfyUI is the rendering engine and Blender is the front end. When a workflow finishes, Blender often needs to know which model was used - the checkpoint, LoRA, or whatever identifier the workflow passes along - so the addon can display it, name outputs after it, or log it. SaveModel is the return channel for that. Its whole implementation is one line: hand the incoming string back to Blender as a UI result.

How it works

• model (STRING) - the only input. It's just text: a model path, a filename, whatever your workflow wants to report back. The author's own tooltip is literally "模型." (Chinese for "model."), which tells you exactly how much ceremony is involved.

It's marked as an output node, and it produces no IMAGE, no tensor, nothing to wire onward. The string travels out-of-band through the pack's bridge - the same websocket plumbing the addon uses to get node lists and queue state from ComfyUI. In Blender, that shows up as the model name attached to the result.

So the honest framing: this node exists so that Blender-facing workflows can round-trip an identifier. If you're working purely in the web UI, there is no reason to ever add it - it's a communication node, not a storage node. Anyone who tells you it's how you export a model is guessing.

Install

It ships with ComfyUI-CUP. ComfyUI Manager → search ComfyUI-CUP, or:

cd ComfyUI/custom_nodes
git clone https://github.com/AIGODLIKE/ComfyUI-CUP.git

then restart. No extra dependencies, no model downloads.

The gotcha

The name actively lies to you. If you add SaveModel expecting a checkpoint file on disk, you'll get nothing and wonder if it's broken. It isn't broken - it's a message-passing node for the Blender bridge, and its value only exists when ComfyUI-BlenderAI-node is running on the other end of that connection. In isolation, the correct reaction to this node is "oh, that's a string sender" and moving on.