Fingers crossed
I really hope for a quick solution
We use Assistants API extensively and do see the new GPT-5 model.
Users are already asking when can they use the new model.
We hope that we could get at least a timeline.
We also use the Assistant API for all of our related texts. We hope to see a significant increase in efficiency by switching to GPT-5. Unfortunately, we cannot see the model in the selection either. We have basically allowed all models, so we have not set anything there. We are Tier 5.
Thanks for sharing this. I can access gpt-5 via this entry.
Assistants was expected to be supported until at least 1Q 2026. Our product—used by hundreds of thousands—relies entirely on it. When GPT-5 launched, Assistants was enabled, so we told our users it was “coming soon.” Now it’s suddenly disabled in the Endpoints, leaving us stuck. Please restore GPT-5 support for Assistants as originally indicated.
Hello, I’m pretty sure I saw assistant api enabled in gpt-5 models, but now it’s grayed out, any news on this? anyplans on bringing gpt-5 models to assistant apis?
What OpenAI is doing to us, clients and users, is, at the very least, disrespectful.
The Assistants API documentation clearly states that the API will be supported until 2026, and even says it will be updated with new models until the end of support.
And now, overnight, without any notice, the GPT-5 documentation says that the Assistants API is not supported - when, until yesterday, it said it was?!
I truly did not expect such behavior from a company of this size, with such a lack of communication.
I hope this is just an isolated communication failure, because we, API users, are not mere users, we are your clients! Our businesses depend on you communicating API changes correctly and clearly.
We rely on Assistants API and HAVE to get GPT-5 supported with it!! @OpenAI, when will it be supported??
Try:
We regret to inform our valued customers that, following thorough internal assessments, the anticipated GPT-5 series will not be integrated with the “Your Files” service. The unpredictable and unmanageable nature of GPT-5 prevents us from ensuring the exceptional experience our current AI models provide. We are committed to sparing our users the disappointment of longing for previous versions, as has been witnessed with OpenAI’s ChatGPT. Our priority is not to chase fleeting trends, but to consistently deliver excellence.
Think the same, if not for the assistant api might aswell use another AI solution. nowadays everyone have, structured output, batch, tool calls. This was the API which set them apart
same issue here. when i got this error below this morning, i decided to migrate to the new responses API.
OpenAI agent update failed: {\n “error”: {\n “message”: “The requested model ‘gpt-5’ cannot be used with the Assistants API.”,\n “type”: “invalid_request_error”,\n “param”: “model”,\n “code”: “unsupported_model”\n }\n}
so i took off today to migrate all my code to the new responses API. and when i started testing, it so happens that you can’t access vector stores and file IDs using the responses API. it has now left me in a dillema.
first, the assistant API doesn’t work with gpt-5 but can work with vector stores. on the other hand, the new response API can work with gpt-5 but cant work with vector stores or file IDs. i need to work with both vector stores and gpt-5. looks like i have to accept and abandon C# and dive into python.
I’m also encountering the exact same issue—GPT‑5 appears in the Playground and via the API, but doesn’t show up within Assistants.
I spent out a lot of time in migrating it to responses api and ended up with knowing RAG is not supported, probably few files can be attached but that too within a message not as a vector store.
It’s probably just a matter of timing, hang tight and keep checking. Hopefully full access appears for all of us soon!
Hi @rodrigoi apologies for the confusion. You are correct, gpt-5 is not supported in the Assistants API. Our team are updating our documentation to reflect the same. Thanks for raising this.
@Colm_Roche what do you mean not supported? Like we all know it is not supported here that is what this conversation is all about. Are you saying it is never going to be supported???
That can be inferred by “updating our documentation”, instead of any other offer such as “updating our legacy APIs to support in-reasoning internal tool use”.
File Search, with Vector Store, IS a tool available on the responses API.
Responses does not have a thread-like message attachment for user message files that automatically populates a thread vector store. By self-management of vector stores created for a session employing user files, you can offer the same level of service.
In fact, the internal instructions of file search, and injection of a cache-breaking unseen message within messages you sent, make file search ONLY a product for a user to talk about their files, not for a developer to improve domain knowlege.
In my case I am relying in the thread-like functionality of the assistant, if you come up with a good alternative could you share it, thanks.
@SamAltman we need chat gpt-5 in assistants api!!!
It sure would have been nice if they just spelled it out, especially at the launch, but I understand it is a thing. FYI everyone according to @_j and @Colm_Roche GPT5 WILL NOT BE SUPPORTED ON ASSISTANTS API. Just spelling it out here for folks who can’t read between the lines. Please anyone correct me if I am wrong
@SamAltman We’re all looking for and looking forward to GPT-5 in Assistants API! This is very important for us ![]()
