On June 3, 2026, OpenAI announced that Agent Builder is scheduled to shut down on November 30, 2026. For teams that choose to carry workflows forward, the practical question is which documented route fits. The official deprecations page says the product is being retired and that ChatKit remains available. The documentation does not specify whether the post-shutdown ChatKit runtime will support existing Agent Builder workflow IDs.
For teams considering migration, it helps to understand the components of a workflow. As defined in the Agent Builder overview, a workflow consists of the agents, tools, and control-flow logic that define an automated process. Previously, these workflows could be published with IDs and deployed by passing the ID into ChatKit or by down the associated SDK code. Teams choosing to migrate have documented options to move toward code-based or workspace-integrated environments. A critical technical detail is that the export process is not a direct translation of a visual workflow graph. As the official migration guide explicitly states: “This process does not convert your workflow graph or guarantee that every behavior transfers unchanged.” Consequently, builders should treat exported code as a starting point rather than a finished replacement for their existing logic.
Migration Routes #
OpenAI documents two primary routes for teams choosing to migrate their workflows. The first path involves moving workflows into the Agents SDK. This route is designed for builders who prefer to manage their agent logic within their own application infrastructure. The process begins by using the Code dialog in the Agent Builder to export the workflow as TypeScript or Python code. Once the code is exported, the builder must copy it into their application, install the matching SDK, and configure the environment. An SDK implementation requires validation of runtime configuration, tools, authentication, permissions, and deployment. Each of these elements must be verified within the target runtime to ensure the application functions as intended.
The second route is intended for organizations utilizing ChatGPT Business, Enterprise, or Edu workspaces. This path requires access to Workspace Agents and the necessary permissions to create them. Builders must paste the exported code into the workspace environment. This process involves configuring apps, tools, skills, authentication, and connection permissions. Because some behavior may need manual recreation, and workflows with strong determinism at their core may not migrate faithfully to a Workspace Agent, builders are directed to preview representative inputs and compare the agent’s behavior against the original workflow’s expected outcomes. Creation of the agent should occur only after this validation phase is complete.
Limitations and Testing #
The need to test representative cases and compare expected behavior follows from the fact that the export process does not guarantee parity. By validating app configuration, authentication, and runtime behavior, builders can identify where manual adjustments are required. Moving from a visual graph to code or a workspace environment involves distinct technical requirements that must be addressed individually. Connected apps, authentication, publishing, and permission configuration require separate review. The migration guide emphasizes that some behavior may need manual recreation, and workflows with strong determinism at their core may not migrate faithfully to a Workspace Agent. Therefore, builders should not assume that exported code will function identically to the original visual workflow without these additional steps.
Unresolved Questions #
The deprecations documentation does not resolve the status of existing hosted workflow IDs. Specifically, it remains unclear whether workflows published through Agent Builder will continue to execute via ChatKit after the November 30, 2026, shutdown. Builders should not assume that ChatKit’s availability guarantees the persistence of these specific workflow IDs. This remains an open question that is not settled by current documentation, so teams relying on these IDs should treat the point as unresolved.
Conclusion #
The shutdown concerns the builder used to compose agent workflows; the documented routes are options for teams that choose to move workflows into application code or Workspace Agents. For teams considering that move, an initial step is to assess which workflows they want to carry forward and what testing the chosen route requires. The documentation does not say that every deployed workflow must move before November 30, and it does not settle whether existing workflow IDs will continue through ChatKit after that date. Route-specific validation lets teams compare resulting behavior with expected outcomes without assuming that an export preserves the original graph or behavior.