So then there’s no way to connect an App that’s built with my own custom front-end (and using the OpenAI API) with my GPTs?
That seems like it’s a missing feature as it means we can’t build GPTs that interact with IoTs…
Maybe I’m misunderstanding something? It seems like GPTs will just be narrowed-down versions of ChatGPT and not powerful things that can interact with user-specific content…
I guess the motivation for going the GPTs route was to take advantage of the upcoming store. We wanted our app to be available to others via the store without us having to market it ourselves.
After some testing, I did find that the API calls to our backend from ChatGPT does pass the conversation id and an ephemeral user id, which expires after 24 hours. Unfortunately, this won’t be useful, since it’s not a persistent value. Seems to be the same as what’s available for plugins.
Yeah I come down to this realization recently, a couple of thoughts:
if you can afford it, make your service stateless so you don’t need to rely on uid, or session id or what not, I know it’s not always feasible but worth a shot;
Use assistant API. You probably lose some traffic from open AI store (in the future), but you gain better control, e.g. uid;
Make some clunky actions that allow user to jump to your login page and you figure out how to wire up whatever in their request and user login event, in my opinion, not worth it.
Am also interested in something like this.
Right now seems like the best solution is to build our own chat as a workaround.
But a feature like this seems like it could be added in the future, rendering the cost/benefit of the effort involved in building our own chats questionable.
What brings me to this conversation is that I am doing the exact above – I require an email verification.
My question is, you know there will be clowns out there trying to impersonate valid users – so is there a way to identify that clown is based upon their ChatGPT acount? The account id, the email, whatever. A temporary id that expires in 24 hours is useless because it will be more than 24 hours before we discover the attempt.
I did all three, but instead of assistants api I used chat completion api. And users don’t have to jump to a login page. And I can still create a GPT and place it in the GPT store.
I had the same issue like you and got stuck. My final approach is to ask the user’s email When The user starts the app.
It’s not a good solution,but at least you won’t get stuck.