OpenOutpainter Serving Style Define

openOutpaint carries over a feature from the A1111 days: "prompt styles," a multi-select list under the prompt box where each entry is a saved prompt + negative prompt pair that gets merged into your generation. On a normal A1111 setup you'd manage those in its settings UI. In this pack, you define them in the workflow itself - that's what OpenOutpainter Serving Style Define is for.

Three required inputs:

• style_name (STRING) - the name that shows up in the canvas's style list.
• prompt (STRING, multiline) - the positive text the style contributes.
• negative_prompt (STRING, multiline) - the negative text.

Plus an optional oop_styles input and the matching oop_styles output. Chain several Define nodes - wire one's output into the next one's optional input - to build up a whole list of styles. The node keeps a dict of styles keyed by name, and a redefined name overwrites the old entry, so later nodes win on collisions. Finally, wire the accumulated oop_styles into the Serving node's optional oop_styles input. From there the API serves it at /sdapi/v1/prompt-styles, and the canvas's multi-select list populates.

How it's meant to be used

The intended flow is the A1111 one: the user checks a couple of styles in the canvas, they get baked into the request, and your workflow has to actually do something with them - which is what the Style Get node is for. But the source comments note this opens up "creative uses outside of the intended use," and that's true. Since a style is just a named prompt/negative pair, you can use the same mechanism for things like mood presets, negative-prompt profiles for different content types, or character sheets - anything where the canvas user picks a label and your graph expands it into text. Nothing about it is tied to the checkbox UI; it's a lookup table with a dropdown on the front.

Install and gotchas

Standard pack install, once for all nodes: ComfyUI Manager (search "OpenOutpaint ComfyUI Interface") or git clone https://github.com/without-ordinary/openoutpaint_comfyui_interface into ComfyUI/custom_nodes, restart. opencv-python is the only dependency worth naming; no models to fetch.

The gotchas are both about forgetting the second half. First, defining styles here does nothing unless the oop_styles output reaches the Serving node - that's the only path to the API. Second, even then, a checked style just rides along in the request; if no Style Get node reads it, the selection is silently ignored and your graph generates without it. Also keep in mind the pack's one-serving-workflow rule - wire the style chain into a single Serving node, not a graph with two.