OpenAI's Assistants API shuts down Aug 26 — 8 days to port your bots
In 8 days, Threads, Runs and Assistants objects stop answering. Here's the Responses + Conversations path — and the parity gaps devs are already hitting.
Copy markdown
What dies Aug 26: the whole beta stack
The Assistants API — Assistants, Threads, Runs and Run Steps — shuts down entirely on August 26, 2026, exactly one year after the deprecation notice. Calls will start failing, so any bot still pointed at those endpoints goes dark unless you've moved first.
Where it maps: Responses + Conversations
Threads become the Conversations API, Runs become Responses, and your Assistant config becomes a dashboard-versioned Prompt. Responses hands back output items synchronously, which means you now own the orchestration — history pruning, tool loops and retries — that the beta ran server-side.
The upgrade: tools the beta never had
The move isn't just survival. The Responses API ships built-in tools the Assistants beta couldn't call — MCP, computer use and deep research, alongside code interpreter and file search — so porting is also how you unlock agent capabilities you were locked out of.
The catch: parity isn't total
Devs on OpenAI's own forum flag gaps: no programmatic way to create Prompts (dashboard-only), missing conversation-truncation controls, and undocumented parameter handling on reasoning models. Budget real test time — this is not a find-and-replace.
Do this week: audit, then stage
There's no auto-converter; OpenAI's advice is to route new conversations to Responses now and backfill old threads. Check your downstream too — Azure OpenAI's Assistants and Zapier's ChatGPT actions ride the exact same Aug 26 sunset.