Agent Builder shuts down on 30 November 2026. Here is how to move off it
The migration off OpenAI's Agent Builder, step by step, with what the export does and does not carry over.
Quick answer
OpenAI shuts down Agent Builder on 30 November 2026. To move off it: list every workflow and where it is used, export each one from Agent Builder as Agents SDK code (Code, then Agents SDK, then TypeScript or Python), rebuild what the export does not carry over, then either run ChatKit against your own server with the openai-chatkit Python package or replace the chat frontend. Internal-only workflows can move to ChatGPT Workspace Agents on a Business, Enterprise or Edu workspace instead.
OpenAI's docs say Agent Builder is scheduled to shut down on 30 November 2026. The notice went up on 3 June, and the deprecations page names two replacements: the Agents SDK, or ChatGPT Workspace Agents. ChatKit, the chat interface many teams put in front of their Agent Builder workflows, stays available.
This guide is the order I would do the move in, with a test at each step. Everything about OpenAI here is from its own docs, read on 20 November 2026.
Step 1: list what you have
For each workflow in Agent Builder, write down four things:
- Where it is used: a ChatKit chat on your site, an internal tool, an API call from your backend.
- Which tools it calls, and which of those change data.
- What it stores between turns, and where.
- Who uses it: customers, or only your own team.
The last answer picks the route. Workflows only your own staff use can go to ChatGPT Workspace Agents, which needs a ChatGPT Business, Enterprise or Edu workspace. Anything customers use needs to run on your own infrastructure.
Step 2: export each workflow as code
In Agent Builder, open Code, choose Agents SDK, then TypeScript or Python. The Agents SDK is OpenAI's open-source framework for agents, MIT-licensed in both languages.
Read the export carefully. OpenAI's own migration page says the process does not convert your workflow graph or guarantee that every behaviour transfers unchanged. Treat the code as a starting point: compare it with the list from step 1 and rebuild anything missing, especially branches, guardrails and tool settings.
Step 3: decide where the chat lives
If customers talk to the workflow through ChatKit, you have two choices.
Keep ChatKit, run your own server. OpenAI's guide describes a custom integration built with the openai-chatkit Python package. You extend a ChatKitServer with your own respond method, implement a Store that keeps threads, messages and files in your database, add a FileStore if users upload files, and use its helpers to run the exported Agents SDK code. For production, the guide asks for durable storage.
Replace the frontend. If you were going to touch the chat anyway, this is the moment. The ChatKit alternatives compares the main options: CopilotKit, assistant-ui and the Vercel AI SDK if you keep building, or Verb if the chat was meant to be an assistant inside your product and you would rather not run one.
Step 4: test it against the saved answers
Run the requests from step 2 through the new version. Check the answers, and check every tool call: which tool, with which values, as which user. A migration that answers the same but calls a tool with different arguments is not finished.
Step 5: switch over before 30 November
OpenAI's pages do not say what happens to hosted workflow IDs after the shutdown date. The ChatKit guide mentions a transition window without giving its end. Plan as if hosted workflows stop on 30 November, switch your site to the new server before then, and keep the old one only as a fallback you can drop.
A checklist to copy
- Every workflow listed, with its users, tools and storage.
- Each one exported to the Agents SDK and compared with the list.
- Missing branches and guardrails rebuilt.
- Chat served from your own server, or a new frontend in place.
- Saved requests give the same answers and the same tool calls.
- Switched over, with time to spare before 30 November.
Once the agent runs on your own infrastructure, it is worth checking it against an in-app agent launch checklist, since some of what Agent Builder handled for you is now yours.
Sources
Each read on 20 November 2026.
Frequently asked questions
When does OpenAI Agent Builder shut down?
On 30 November 2026. OpenAI announced the deprecation on 3 June 2026, and its deprecations page names the Agents SDK or ChatGPT Workspace Agents as the replacements.
Can I export an Agent Builder workflow to code?
Yes. In Agent Builder, open Code, choose Agents SDK, then TypeScript or Python. OpenAI says the export does not convert your workflow graph or guarantee that every behaviour transfers unchanged, so treat it as a starting point and test each workflow end to end.
Will my hosted ChatKit workflow keep working after 30 November?
OpenAI's pages, read on 20 November 2026, do not say what happens to hosted workflow IDs after the date. They describe a transition window without giving its end. Plan as if hosted workflows stop on 30 November and move to your own server before then.
What do I need to run ChatKit on my own server?
OpenAI's guide uses the openai-chatkit Python package: a ChatKitServer you extend with your own respond method, a Store that saves threads, messages and files in your database, and a FileStore if users upload files. Its helpers connect the server to the Agents SDK.

Vishnu, founder of AskVerb @itsvishnups
Building the AI agent that lives inside a SaaS product and does the work its users ask for. Writing down what I learn along the way, including the parts I got wrong first.