Aiv Param

Aiv Param is the bridge between a ComfyUI workflow and people who will never open ComfyUI. You build the full graph - loaders, samplers, face restore, the works - and this node turns the few knobs you care about into a clean form: a prompt box, a seed, a steps slider, an image upload. Your end users tweak that form inside the AIV platform (WeChat mini-programs, web apps, native apps) and the AIV agent runs your exported workflow behind the scenes. It's the "parameterize my workflow for customers" play.

Which means the honest caveat up front: if you're not publishing through AIV's platform with their aivagent Python SDK (pypi.org/project/aivagent, the platform itself is aiv.store), this node does literally nothing for you. It has no outputs. It doesn't run code. It's a JSON config blob plus a frontend nicety, useless as a standalone utility. That's a feature, not a bug - it's a deployment tool, aimed at builders shipping AI apps in the Chinese ecosystem where mini-programs are the default distribution channel.

How it actually works

The server side is a joke in the best way: execute() is literally pass. All the work happens in js/check.js, which hooks the node's text_param widget and overrides its value getter/setter. When ComfyUI saves the workflow, the getter escapes every { and } with a backslash so your nested JSON survives serialization and can be json.loads()'d on the other end; when it renders the textarea, the setter strips those escapes back off so what you see is clean, valid JSON. That's the entire mechanism - no API calls, no models, no GPU. It's a frontend formatting node wearing a utility costume.

You interact with it through two multiline text fields, and only one matters:

• text_param - the JSON array of parameters you're exposing. This is the whole node.
• text_note - a read-only-ish usage manual the author ships as the default. Leave it be.

There are no outputs, and you don't wire anything in or out. The node's job is to be read, not connected.

The JSON you actually write

Each element of the array is one exposed parameter. Only two fields are mandatory: id (the ComfyUI serial number of the node whose input you're exposing - export your workflow to API JSON if you don't know it) and name (that node's parameter name, e.g. seed, steps, text). Everything else is optional but useful:

[
  {"id": 18, "name": "text", "title": "提示词", "option": {"type": "text", "multi": true, "tooltip": "prompt goes here"}},
  {"id": 30, "name": "seed", "title": "Seed", "default": 512356789158, "option": {"type": "seed"}},
  {"id": 21, "name": "steps", "title": "Steps", "option": {"type": "number", "min": 1, "max": 100, "step": 1}},
  {"id": 117, "name": "image", "title": "Upload", "required": true, "option": {"type": "file", "ext": ".jpeg,.png,.webp"}}
]

The option.type drives what widget the end user gets: text, number, bool, seed, combo (a dropdown - pass values), or file (upload, with min/max size limits and ext filters, including variables like $audio or $video). order sorts them (bigger first, default 10) and title is the label. The author's sample even shows exposing a face-restore model as a combo - but note that GFPGAN/GPEN only appear in the example text; this pack downloads nothing.

Installing it

Easiest via ComfyUI Manager - search "AIV ComfyUI Node" (author bbtaivi, it's in the registry) and install. Or the manual way:

cd ComfyUI/custom_nodes
git clone https://github.com/bbtaivi/ComfyUI-Aiv-Param

Restart ComfyUI. There's no requirements.txt, no pip deps, no model downloads - the whole pack is one Python file, one JS file, and an image. It's as lightweight as custom nodes get.

Where people get burned

• Valid JSON, always. The node won't throw a helpful error on a stray comma - it just won't do what you expect. The author suggests checking your array in an online JSON validator before you fight it.
• One AivParam per workflow, period. The docs are explicit. If you need more, restructure, don't duplicate.
• Wrong id. Get the node serial wrong and you're silently exposing a different node's parameter. Export → API is your friend.
• clear is on by default. For text params, the input auto-clears after a task runs unless you set "clear": false. Great for prompts, infuriating if you didn't expect it.

It's a niche, single-purpose node with zero community footprint - but if you're shipping AIV apps, it's the whole interface between your graph and your users.