OpenAI Agent Builder Shuts Down November 30, 2026: How to Export Your Workflows and Where to Go Next
Updated November 16, 2026 · Dates and steps checked against OpenAI’s official documentation on November 16, 2026
OpenAI Agent Builder shuts down on November 30, 2026. That is two weeks from today. OpenAI’s deprecations page lists Agent Builder as “Deprecated” with a shutdown date of November 30, 2026, a notice date of June 3, 2026, and two recommended replacements: the Agents SDK or ChatGPT Workspace Agents. ChatKit, the toolkit many teams used to put Agent Builder workflows on their websites, “remains available” (OpenAI deprecations).
If you built a workflow on the Agent Builder canvas, nothing will move itself. You need to export your workflow as code before the deadline and choose where it will run next. This guide covers the exact export steps OpenAI documents, how to choose between the two official paths, what will not transfer cleanly, and the third-party tools worth a look if you want to leave OpenAI’s stack.
Quick answer: what is happening to OpenAI Agent Builder?
| Question | Answer (from OpenAI’s docs) |
|---|---|
| Shutdown date | November 30, 2026 |
| When it was announced | June 3, 2026 (notice date on the deprecations page) |
| Can I still use it now? | Yes. “Existing users can continue using it during the transition window.” |
| Official replacements | Agents SDK (code) or ChatGPT Workspace Agents (natural language, for teams) |
| Does ChatKit go away? | No. ChatKit remains available. |
| Is the workflow graph converted automatically? | No. OpenAI says the process “does not convert your workflow graph or guarantee that every behavior transfers unchanged.” |
Agent Builder is not the only thing ending that day. The same OpenAI table lists the /v1/prompts endpoint and reusable prompt objects as shutting down on November 30, 2026, with the advice to move prompt content into your application code, and puts the Evals dashboard, API and graders into read-only mode on the same date, with Promptfoo named as the migration target. If your workflows used saved prompt objects or OpenAI Evals, plan for all three at once.
Step 1: export every workflow as Agents SDK code
OpenAI’s Migrate from Agent Builder guide describes one export method for both paths:
- Open your workflow in Agent Builder.
- Select Code in the top navigation.
- Select Agents SDK in the code dialog.
- Select TypeScript or Python, then copy the complete export.
Do this for every workflow, including ones you think are unused, and save each export in version control with a short note: what the workflow does, which tools and connectors it calls, which ChatKit embed or app uses its workflow ID, and two or three real test inputs with the outputs you expect. That note is your acceptance test after the move. Take screenshots of the canvas too. The exported code is the logic; the screenshot is the only record of how the graph looked.
Step 2: choose your migration path
Option 1: the Agents SDK (for developers)
OpenAI recommends this path “when you want to run the exported workflow in an application you build and deploy.” You paste the TypeScript or Python export into your app, install and configure the matching Agents SDK, and test it in your own runtime. You get full control over orchestration, tools and state, and you take on hosting, authentication, permissions and monitoring yourself. OpenAI’s Agents overview also lists the Agents API (an agent run on the Codex harness that OpenAI manages), the Responses API for direct model calls, and ChatKit for embedded chat, so pick the runtime that matches how much of the loop you want to own.
Option 2: ChatGPT Workspace Agents (for teams)
This path suits people who built agents for internal work and want to share them with colleagues. You need a ChatGPT Business, Enterprise or Edu workspace with access to workspace agents and permission to create them. OpenAI’s steps: open a new workspace agent in ChatGPT, paste your exported code with the prompt “Please help me convert this workflow into an agent:”, review anything the builder flags as needing changes, configure apps, tools, skills and connection permissions, then use Preview with real inputs before you select Create.
Which one should you choose?
- Your workflow powers a customer-facing chat on your site: Agents SDK, keeping ChatKit as the front end if you already use it.
- Your workflow is an internal helper for a team already on ChatGPT Business or Enterprise: Workspace Agents.
- Your workflow is highly deterministic (fixed branches, strict routing, exact output formats): Agents SDK. OpenAI warns that “workflows with strong determinism at their core may not migrate faithfully to a workspace agent.”
Step 3: check what will not carry over
OpenAI is open about the limits. Expect manual work on:
- Control flow and triggers. Branches, loops and routing on the canvas become code or instructions. Review them line by line.
- Connected apps, authentication and permissions. These need a separate review in ChatGPT, or a new setup in your own runtime.
- Publishing and versioning. Agent Builder versions were snapshots with a workflow ID. After the move, your Git history or the workspace agent becomes the record.
- Safety guardrails. OpenAI asks you to keep the same safety practices, “especially when the agent can access private data or take actions through connected tools.”
One open question: OpenAI’s pages say ChatKit stays available, but we could not find a statement on whether ChatKit embeds that point to an Agent Builder workflow ID keep working after November 30. Treat that as unconfirmed and test a migrated version before the deadline rather than after it.
Non-OpenAI alternatives to Agent Builder
If you would rather not depend on another OpenAI product, these active tools in our database cover the same “build an agent workflow visually or in plain language” job:
- n8n: a fair-code workflow automation tool with AI agent nodes that you can self-host or use in the cloud. The closest match for a node-based canvas you control.
- Make: a visual no-code automation platform with AI modules and agents, good for complex multi-step automations.
- Zapier Agents: describe a job in plain language and an agent runs it through Zapier’s app integrations.
- Lindy: no-code AI assistants for email triage, scheduling, research and multi-step work across apps.
A word of caution from the graveyard: visual agent builders have had a hard 2026. Flowise announced it was winding down in July, saying developers were turning to coding agents for complex tasks, and Relay.app shut down in September and deleted all accounts and workflows. Whatever you choose, keep your logic exportable as code and keep your own copy. That habit is why this migration is possible at all.
Your two-week checklist
- Today: list every Agent Builder workflow and everything that calls its workflow ID.
- This week: export each one as Agents SDK code (TypeScript or Python) and commit it with test inputs.
- This week: check whether you also rely on
/v1/promptsprompt objects or OpenAI Evals, which change on the same date. - By November 25: run each migrated agent side by side with the original on the same inputs.
- Before November 30: switch production traffic and keep the exports archived.
For other recent shutdowns, see our October 2026 AI tool shutdowns roundup, browse the Agents category on the AI tools status list, and learn the early warning signs in the anatomy of an AI tool shutdown.
FAQ
When does OpenAI Agent Builder shut down?
On November 30, 2026, according to OpenAI’s deprecations page. It was marked deprecated on June 3, 2026.
Can I still use Agent Builder now?
Yes. OpenAI says existing users can keep using it during the transition window, which ends with the November 30 shutdown.
What does OpenAI recommend instead of Agent Builder?
The Agents SDK for building agents in code, or ChatGPT Workspace Agents for building and sharing agents in natural language. ChatKit remains available.
Will my workflow convert automatically?
No. You export the workflow as Agents SDK code, and OpenAI says the process does not convert the workflow graph or guarantee identical behavior. Test every migrated agent.
Is ChatKit shutting down too?
No. OpenAI’s deprecations page and Agent Builder guide both say ChatKit remains available.
Sources
- OpenAI: Deprecations (Agent Builder, /v1/prompts and Evals rows, checked Nov 16, 2026)
- OpenAI: Migrate from Agent Builder
- OpenAI: Agent Builder guide (deprecation notice)
- OpenAI: Agents overview (Agents API, Agents SDK, Responses API, ChatKit)
- OpenAI: Migrate from prompt objects
- OpenAI Cookbook: Moving from OpenAI Evals to Promptfoo
Related articles
Open-Source Lifeboats: Where Users Swim When a Tool Sinks
Every shutdown triggers the same migration pattern. The beneficiaries are rarely the dead tool's commercial rivals — they're the open…
Conductor Isn’t Shutting Down After All: What the Meta Deal Means for Users (November 2026)
Conductor joined Meta and planned to close Conductor Cloud on November 20, 2026, then reversed course on November 12-13. What…
12 New AI Tools This Week (Oct 17–31, 2026): Agents, Browsers and Data Apps
Twelve new AI tools launched in the second half of October 2026, from voice agents and AI email to a…
