We have a couple of assistants in production use which were created with the v1 API and have documents attached to them.
We noticed that these assistants don’t use the associated documents anymore. To be precise, sometimes they still respect them in the playground, but not if we run a message thread via the API.
I assume this has something to do with the additional “vector stores” layers that OpenAI built it. But I would have expected that old assistants had been migrated to the new structure.
Also, I am pretty confused that the v1 Assistants API is now marked as “legacy”, while the v2 API is marked as “Beta”. Which one is the API that should be used for production then?!
As another side-note: I am wondering why the API endpoints still use “v1”. This is also pretty confusing.
Is there a way to get the “old” assistants back to work without creating all of them “from scratch”, using the new API?
1 Like
OpenAI and consistency don’t go well together.
Understandably. They are changing things and upgrading constantly.
Assistants is still considered a beta product. You should upgrade when possible. There isn’t that much of a difference with the old version
You need to use the new version for newer models as well such as GPT-4o
2 Likes
I am comparing the APIs as we speak, and there are in fact a lot of differences compared to v1. Is there a news feed or whatsoever to get notified about such changes?
I can understand that everything is a “moving target”. Yet I do not understand why they can’t at least upgrade existing assistants so they still work. It should not be that complex to auto-setup vector stores, link the existing files to them and then linking the vector store to the assistant.
They did upgrade assistants… to V2.
I can understand the frustration but it takes less than 5 minutes to make the adjustments.
https://platform.openai.com/docs/assistants/migration/agents
The new system has different schemas. Therefore you need to have a matching schema to accept it. If you don’t, you use older technology.
Hopefully the link helps. Again, yeah it’s frustrating but it’s expected with beta products in a rapidly changing industry
1 Like
I have a customGPT for work (made via GPT Builder) and for at least the last 24 hours, I’m experiencing the same thing – it also isn’t capable of using its associated documents anymore. Could this be related to the API ‘upgrade’?
Is creating a v2 Assistant a better method and is this difficult for someone without a coding or app developer background?
No, this isn’t related to any ChatGPT GPT issues.
If you want more control and freedom then Assistants are a great choice, but as with any sort of control and freedom, you need to put a lot more effort and work in it make it worthwhile.
1 Like
See the Changelog page. I check it everyday for any API changes.
2 Likes
Haha, that was a good joke.
First, my main complaint is not about the API changes as such, but that assistants created with API v1 don’t work anymore, if they reference files. Even if you use v1 to run the threads. So effectively, the assistants’ functionality is broken in production, until we re-create them from scratch (then, sometimes it works again, even with v1; but not if you just run threads on them, e.g. for end-users).
Second, I’m already working quite some hours on the transformation of the API. If you mapped everything to TypeScript types and are using the APIs intensely, you’ll have to update a lot, not just the pure API calls. There’s also quite some subtle changes not mentioned in these migration docs.
I write in TypeScript as well and had a chat wrapper for Assistants fully utilizing the API. It does not take more than 5 minutes. There’s some seriously wrong if it does.
Regardless, it needs to be done. Knowing it’s a beta product in the future you should consider making life a bit easier for yourself by writing code that can be easily changed without having to deal with a bunch of “subtle changes”.
Again, it’s frustrating but this is expected with any beta products. We all have to deal with it and it usually results in better services. If you’re having a hard time you can always hire someone to get the job for you and see what’s making it so difficult