Tuesday, November 3, 2026
Trend Instant News: stay informed, stay ahead

OpenAI Agent Builder, Evals and Prompts Shut Down November 30: What to Do Now

OpenAI shuts down Agent Builder, the Evals platform and the v1/prompts API on November 30, 2026. Here is the replacement for each and how to migrate.

• 3 min read
Text size
|
Share
OpenAI Agent Builder, Evals and Prompts Shut Down November 30: What to Do Now
Software & SaaS

The OpenAI Agent Builder deprecation takes effect on November 30, 2026. On the same day OpenAI shuts down the Evals dashboard and API and the v1/prompts API for reusable prompt objects. OpenAI announced all three on June 3, 2026 on its official deprecations page. If you use any of them, you have under four weeks to move.

OpenAI Agent Builder deprecation: what shuts down and what replaces it

ProductKey datesOpenAI's suggested path
Agent BuilderShuts down Nov 30Agents SDK or ChatGPT Workspace Agents
Evals (dashboard and API)Read-only from Oct 31, shuts down Nov 30Migration path to Promptfoo
Reusable prompts (v1/prompts)Shuts down Nov 30Move prompt content into your application code

OpenAI states that ChatKit remains available. If your ChatKit front end runs on an Agent Builder workflow, though, you still need to move that workflow.

How to migrate from Agent Builder

OpenAI's migration guide gives two routes.

Route 1: the Agents SDK

  1. Open your workflow in Agent Builder and select Code in the top navigation.
  2. Choose Agents SDK, pick TypeScript or Python, and copy the full export.
  3. Add the code to your app, then install and configure the matching Agents SDK.
  4. Test the workflow in your own runtime before you deploy.

OpenAI warns that the export does not convert your workflow graph or guarantee every behaviour transfers unchanged. Test real inputs side by side.

Route 2: ChatGPT Workspace Agents

This needs a ChatGPT Business, Enterprise or Edu workspace with workspace agents turned on. Create a workspace agent, paste the exported code with the provided prompt, then review the instructions it generates. Set up apps, tools, authentication and permissions. Use Preview to test, and select Create only once it behaves like the original.

OpenAI notes that workflows that rely on strict, step-by-step logic may not migrate faithfully to a workspace agent. Those are better suited to the SDK.

How to move off OpenAI Evals

  • Your existing evals became read-only on October 31. Export results and datasets you want to keep now.
  • Follow the Promptfoo migration guide to rebuild test suites.
  • Remove any CI jobs that call the Evals API before November 30, or they will start failing.

How to replace reusable prompt objects

Find every request that passes a prompt ID. Copy each prompt's text, variables and version into your codebase or config. Then send the full prompt in the request instead. OpenAI's prompt object guide walks through it.

Your November 30 checklist

  • Search your code for Agent Builder workflow IDs, Evals API calls and prompt IDs.
  • Export Agent Builder workflows to Agents SDK code.
  • Export eval data and set up a replacement test runner.
  • Inline every reusable prompt.
  • Run a full test pass in staging before the deadline.

Which route should you pick?

If your workflow…Best fit
Runs inside your own product or APIAgents SDK
Needs strict, repeatable stepsAgents SDK
Is used by staff inside ChatGPTWorkspace Agents (Business, Enterprise or Edu)

Frequently Asked Questions

Can I still view my old evals?

Until November 30, yes, but they have been read-only since October 31. Export anything you need now.

When is OpenAI Agent Builder shutting down?

November 30, 2026.

Is ChatKit being deprecated too?

No. OpenAI says ChatKit remains available.

What replaces the OpenAI Evals platform?

OpenAI does not name a replacement product. It points to a migration path to Promptfoo.

Summary

OpenAI Agent Builder, Evals and the v1/prompts API all shut down on November 30, 2026. Export Agent Builder workflows to the Agents SDK or a Workspace Agent, move evals to Promptfoo, and put prompts in your own code.

Hamza

Editorial team

We cover gaming, software, tech, AI and trading. Every story links to its primary sources, and rumours are labelled as such. Spotted a mistake? Let us know and we will correct it.

Comments

Comments are checked before they appear. Please be respectful and keep to the topic. See our privacy policy.

Loading comments…