compine_chat_messages _O

Let's start with the elephant in the name: it's spelled "compine". Not a typo on this page - a typo in the pack itself, shipped as the node's name and then frozen in every workflow that used it. That's your first clue that compine_chat_messages _O is a relic, not something you should reach for fresh.

This is the deprecated twin of combine_chat_messages _O. Same job, same inputs, same output, different address in the menu. It lives under O/deprecated/OpenAI/Advanced/ChatGPT, which in this pack is ComfyUI's way of saying "keep this around so saved workflows still load, but pretend it isn't there otherwise." If you're building a new graph, use the non-deprecated combine_chat_messages _O and don't look back. If you opened a workflow from an image and found this node in it, the only question that matters is whether it still runs.

What it does (when it runs)

The mechanics are identical to its modern twin - merge two message lists, in order:

• message1 (OPENAI_CHAT_MESSAGES)
• message2 (OPENAI_CHAT_MESSAGES)
• output: OPENAI_CHAT_MESSAGES

The source literally does message1["messages"] + message2["messages"] and returns the joined list. It's how you build the system-message-then-user-message stack that Chat completion _O wants to see before it'll give you a useful reply.

Why it's deprecated

Deprecation here is about the surrounding suite, not the combiner itself. This whole OpenAI wing of the pack predates the OpenAI SDK 1.0 rewrite. The node it pairs with on the old path, Chat_Completion _O, calls the legacy API (openai.ChatCompletion.create) that no longer exists in a modern openai install - and since the pack auto-installs whatever the latest openai wheel is, those old calls fail. The pack's own metadata is candid: "Currently, this extension does not support the new OpenAI API, leading to compatibility issues." So even if this node's list-merging works perfectly, the deprecated pipeline around it can't reach the API anymore. That's why the newer combine_chat_messages _O was born: same logic, wired to the current client-based flow (load_openAI _O → Chat_Message _O → Chat completion _O).

What to do when you hit it

If you load an old workflow and this node appears with a red "missing" state, your options are: rewire the messages through the modern combine node (the OPENAI_CHAT_MESSAGES type is the same on both), or pin an ancient openai version in your Python env - which you don't want to do, because it'll break every other modern OpenAI integration you've got. Rewire it. It's two inputs and one output; it takes about thirty seconds and removes a known-broken link from the chain.

Install

It ships in the Quality of Life Suit pack (all nodes under the O/ menu), installed once via Manager - search "Quality of Life Suit" - or:

cd <ComfyUI root>/custom_nodes
git clone https://github.com/omar92/ComfyUI-QualityOfLifeSuit_Omar92.git

Restart ComfyUI afterward; a page refresh won't register new nodes. Note the pack auto-updates on every start using a generated config.json - set "autoUpdate": false there if you'd rather it stop yanking the rug out. And if a future update removes this node entirely, that's the deprecation working as intended.