OpenAI reusable prompt objects and v1/prompts are scheduled to shut down November 30, 2026
OpenAI announced reusable-prompt deprecation on June 3, 2026. The documented November 30 shutdown covers reusable prompt objects and v1/prompts. Move managed prompt content into application-owned code before that date.
Kingy verdict
Treat saved OpenAI prompt objects as a migration dependency before November 30. Move their content and variables into application code, then validate the generated requests before changing production callers. A completed Assistants migration can still leave this separate dependency in place.
Required action
Inventory saved prompt IDs, versions and variables. Move prompt content into versioned application helpers, generate Responses input/instructions directly, and validate behavior before switching production callers. Avoid a new long-lived prompt-object dependency.
What is scheduled to change
OpenAI announced the reusable-prompt deprecation on June 3, 2026. Its current schedule lists November 30, 2026 for shutdown of reusable prompt objects and v1/prompts. The notice covers the managed prompt feature used through the dashboard and API. It gives a date without an exact cutoff time or timezone.
Move the prompt into your application
Inventory the saved prompt IDs, versions and variables that callers depend on. OpenAI recommends storing prompt content in code, replacing variables with explicit function arguments, and passing generated content directly through Responses input and instructions. Version the helpers with the application and test representative requests before switching callers.
Read the Assistants migration caveat
The official Assistants migration page retains a create-prompt step, followed by a warning that reusable prompt objects are also deprecated. Use the current prompt-object migration guide when planning a lasting replacement. Evals has its own October 31 read-only milestone; that date does not belong to reusable prompts. Agent Builder also has a November 30 shutdown, for a separate product.
Keep caching expectations testable
The migration guide recommends placing static prompt content before dynamic content because cache hits depend on exact prefixes. Moving prompts into code alone establishes no cache hit, latency improvement or cost saving. Its code examples do not establish a required model upgrade or tested compatibility with your installed SDK.
Evidence limits
Historical first-detection date is unverified. The June 3 notice and this source review do not establish when Kingy first detected the change. No account, saved prompt, SDK request, migration, response quality, cache hit or cost was tested. This record describes a scheduled change; it does not confirm that a shutdown has occurred.
Related Kingy coverage
Our Assistants migration article already warns about this separate prompt-object deadline. This record covers the reusable-prompt dependency; the Assistants article keeps its own history and migration scope.