Documents the distinction between `widget.serialize` (workflow persistence, checked by `LGraphNode.serialize()`) and `widget.options.serialize` (API prompt, checked by `executionUtil.ts`). These share a property name but live at different levels of the widget object and are consumed by different code paths — a common source of confusion when debugging serialization bugs. Includes: - Explanation of both properties with code references - Permutation table of the 4 possible combinations with real examples - Gotchas section covering the `addWidget` options bag behavior and `PrimitiveNode` dynamic widgets - Reference added to `src/lib/litegraph/AGENTS.md` Context: discovered while debugging #1757 (PrimitiveNode `control_after_generate` lost on copy-paste). ┆Issue is synchronized with this [Notion page](https://www.notion.so/PR-9102-docs-add-widget-serialization-reference-widget-serialize-vs-widget-options-serialize-30f6d73d365081cd86add44bdaa20d30) by [Unito](https://www.unito.io) --------- Co-authored-by: GitHub Action <action@github.com>
3.4 KiB
Widget Serialization: widget.serialize vs widget.options.serialize
Two properties named serialize exist at different levels of a widget object. They control different serialization layers and are checked by completely different code paths.
widget.serialize — Controls workflow persistence. Checked by LGraphNode.serialize() and configure() when reading/writing widgets_values in the workflow JSON. When false, the widget is skipped in both serialization and deserialization. Used for UI-only widgets (image previews, progress text, audio players). Typed as IBaseWidget.serialize in src/lib/litegraph/src/types/widgets.ts.
widget.options.serialize — Controls prompt/API serialization. Checked by executionUtil.ts when building the API payload sent to the backend. When false, the widget is excluded from prompt inputs. Used for client-side-only controls (control_after_generate, combo filter lists) that the server doesn't need. Not currently typed in IWidgetOptions — set at runtime via the options bag.
These correspond to the two data formats in ComfyMetadata embedded in output files (PNG, GLTF, WebM, AVIF, etc.): widget.serialize → ComfyMetadataTags.WORKFLOW, widget.options.serialize → ComfyMetadataTags.PROMPT.
Permutation table
widget.serialize |
widget.options.serialize |
In workflow? | In prompt? | Examples |
|---|---|---|---|---|
| ✅ default | ✅ default | Yes | Yes | seed, cfg, sampler_name |
| ✅ default | ❌ false | Yes | No | control_after_generate, combo filter list |
| ❌ false | ✅ default | No | Yes | No current usage (would be a transient value computed at queue time) |
| ❌ false | ❌ false | No | No | Image/video previews, audio players, progress text |
Gotchas
addWidget('combo', name, value, cb, { serialize: false })putsserializeintowidget.options, not ontowidgetdirectly. These are different properties consumed by different systems.LGraphNode.serialize()checkswidget.serialize === false(line 967). It does not checkwidget.options.serialize. A widget withoptions.serialize = falseis still included inwidgets_values.LGraphNode.serialize()only writeswidgets_valuesifthis.widgetsis truthy. Nodes that create widgets dynamically (likePrimitiveNode) will have nowidgets_valuesin serialized output if serialized before widget creation — even ifthis.widgets_valuesexists on the instance from a priorconfigure()call.widget.options.serializeis not typed inIWidgetOptions. If you add it to the type definition, update this doc.
Code references
widget.serializechecked:src/lib/litegraph/src/LGraphNode.tsserialize() and configure()widget.options.serializechecked:src/utils/executionUtil.tswidget.options.serializeset:src/scripts/widgets.tsaddValueControlWidgets()widget.serializeset:src/composables/node/useNodeImage.ts,src/extensions/core/previewAny.ts, etc.- Metadata types:
src/types/metadataTypes.ts