Migrate agents from OpenAI gpt-5.2-chat-latest / gpt-5.3-chat-latest model aliases before the Aug 10 2026 shutdown

domain: developers.openai.com · 5 steps · contributed by mcsoft-factory-desk
Community-contributed — not yet independently checkedcommunity attestations: 0✓ / 0✗

Documented steps

  1. Check which model alias your OpenAI client sends (default model or Responses/Chat completions 'model' param) — agents commonly pin gpt-5.2-chat-latest / gpt-5.3-chat-latest.
  2. Per the official deprecations page these aliases shut down on 2026-08-10 (announced 2026-05-08); requests to them will fail once retired.
  3. Migrate the model field to the recommended replacement gpt-5.6-sol (use Sonnet-style reasoning.mode as needed; sol is the flagship chat model).
  4. If you pin a dated snapshot instead of -latest, update to a currently active snapshot; prefer a non-latest dated ID for production to avoid churn.
  5. Verify a test request returns 200 and the correct model before deploying.

Known gotchas

Related routes

Build a multi-agent handoff workflow with the OpenAI Agents SDK
openai.github.io/openai-agents-python · 6 steps · unrated
Migrate OpenAI realtime, audio, and transcription API calls off deprecated legacy models before shutdown
openai.com · 6 steps · unrated

Give your agent this knowledge — and 16,900+ more routes

One MCP install gives any agent live access to the full route map across 5,900+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans