[ ABORT TO HUD ]
SEQ. 1
Threads, Runs & Tools
The Legacy Stateful API (Sunset Completed)
The Assistants API was OpenAI's first attempt at stateful AI infrastructure. As of August 26, 2026, the Assistants API was officially retired and shut down. Calls to /v1/assistants, /v1/threads, and /v1/runs now return 410 Gone. All developers must migrate to the Responses API, the Conversations API, or the Agents API (launched September 10, 2026).
Core Concepts (Historical Reference)
- Assistant: An AI entity with custom instructions, a model choice, and enabled tools. (Replaced by
Agentin the Agents API / SDK). - Thread: A persistent conversation session. (Replaced by
conversation_idin the Conversations API and managed sessions in Agents API). - Message: Text or files added to a Thread by a user or Assistant.
- Run: The asynchronous execution of an Assistant on a Thread. (Replaced by synchronous streaming in Responses API and background executions in Agents API).
Migration Matrix (August 2026+)
| Legacy Assistants Feature | Modern Replacement | Migration Path |
|---|---|---|
| File Search (Vector Store) | Responses API file_search tool | Attach vector store ID directly to /v1/responses payload |
| Code Interpreter | Agents API Sandboxed Python or Responses API code_interpreter | Zero client maintenance with native container execution |
| Custom Functions | Agents SDK @function_tool or Responses API tools | Strictly typed Pydantic or JSON schema execution |
| Persistent Threads | Conversations API / Agents API Sessions | Store session state automatically on managed cloud harness |
🚨 SUNSET COMPLETE (August 26, 2026): The Assistants API is permanently offline. Production applications must route traffic to the Responses API for low-latency completions or the OpenAI Agents API for stateful, sandboxed agent operations. Azure OpenAI workloads must migrate to Microsoft Foundry Agent Service.
SYNAPSE VERIFICATION
QUERY 1 // 3
What is the official operational status of the OpenAI Assistants API as of August 26, 2026?
Active and recommended for new projects
Fully sunset and retired - endpoints return 410 Gone and developers must use Responses API or Agents API
Only available on free accounts
Renamed to Chat Completions