Describe the bug
Found with arol, a deprecation scanner I built after a vendor retirement broke our own production
The OpenAIAssistant agent node is built on OpenAI's Assistants API (beta), which is being removed on August 26, 2026 — under four weeks out (https://platform.openai.com/docs/assistants/migration). After that date the node's calls will be rejected, affecting every deployed flow that uses it.
References:
packages/components/nodes/agents/OpenAIAssistant/OpenAIAssistant.ts:180 (beta.threads), :256, :266, :269 (beta.assistants)
OpenAI's migration path is the Responses API + Conversations API. Given the timeline, even a deprecation warning in the node's UI before Aug 26 would save users from silent flow breakage.
Two smaller items in the same scan, flagging while I'm here:
- Gemini default list includes
gemini-2.5-pro / flash / flash-lite (packages/components/nodes/chatmodels/ChatGoogleGenerativeAI/ChatGoogleGenerativeAI.ts:98), scheduled for shutdown Oct 16, 2026 per https://ai.google.dev/gemini-api/docs/deprecations.
- Housekeeping:
moment (maintenance mode) in components/server, react-scripts (CRA, deprecated) in ui, eslint@8 (EOL Oct 2024).
Happy to help with the Assistants→Responses migration PR if useful.
To Reproduce
- Create a chatflow using the OpenAI Assistant agent node, linked to any OpenAI Assistant.
- Run the flow; it works today.
- On or after August 26, 2026, the same flow fails: the node's calls to the Assistants API (client.beta.assistants / beta.threads in packages/components/nodes/agents/OpenAIAssistant/OpenAIAssistant.ts:180, 256, 266, 269) will be rejected, because OpenAI is removing the Assistants API on that date: https://platform.openai.com/docs/assistants/migration
Expected behavior
Flows built on the OpenAI Assistant node keep working past Aug 26; either the node migrates to OpenAI's replacement (Responses API + Conversations API), or at minimum it surfaces a deprecation warning in the UI before the shutdown so users can migrate their flows in time.
Screenshots
No response
Flow
No response
Use Method
None
Flowise Version
No response
Operating System
None
Browser
None
Additional context
No response
Describe the bug
Found with arol, a deprecation scanner I built after a vendor retirement broke our own production
The OpenAIAssistant agent node is built on OpenAI's Assistants API (beta), which is being removed on August 26, 2026 — under four weeks out (https://platform.openai.com/docs/assistants/migration). After that date the node's calls will be rejected, affecting every deployed flow that uses it.
References:
packages/components/nodes/agents/OpenAIAssistant/OpenAIAssistant.ts:180(beta.threads),:256,:266,:269(beta.assistants)OpenAI's migration path is the Responses API + Conversations API. Given the timeline, even a deprecation warning in the node's UI before Aug 26 would save users from silent flow breakage.
Two smaller items in the same scan, flagging while I'm here:
gemini-2.5-pro/flash/flash-lite(packages/components/nodes/chatmodels/ChatGoogleGenerativeAI/ChatGoogleGenerativeAI.ts:98), scheduled for shutdown Oct 16, 2026 per https://ai.google.dev/gemini-api/docs/deprecations.moment(maintenance mode) in components/server,react-scripts(CRA, deprecated) in ui,eslint@8(EOL Oct 2024).Happy to help with the Assistants→Responses migration PR if useful.
To Reproduce
Expected behavior
Flows built on the OpenAI Assistant node keep working past Aug 26; either the node migrates to OpenAI's replacement (Responses API + Conversations API), or at minimum it surfaces a deprecation warning in the UI before the shutdown so users can migrate their flows in time.
Screenshots
No response
Flow
No response
Use Method
None
Flowise Version
No response
Operating System
None
Browser
None
Additional context
No response