Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explore the possibility for chat-ui to use OpenAI assistants API structure. #838

Open
CakeCrusher opened this issue Feb 17, 2024 · 3 comments
Labels
back This issue is related to the Svelte backend or the DB enhancement New feature or request good first issue Good for newcomers

Comments

@CakeCrusher
Copy link

Hi @nsarrazin , I wanted to explore how we could collaborate in making chat-ui more work with OpenAI standards to make it more less opinionated over hosted inference provider. I need it as I am part of a team open-sourcing the GPTs platform https://github.com/OpenGPTs-platform and we will be leveraging chat-ui as the client. So I was hoping we could align our objectives so that we can have a healthy collaboration instead of just diverging. The main point I wanted to touch on is as follows.

Is there any interest in transforming the backend to one that follows the OpenAI assistants API structure so that we may better align ourselves to the OpenAI standard? Based on the disord ⁠announcement "...Message API with OpenAI compatibility for HF...", HF seems to signal that they are pushing in that direction so it would make sense to support that on the chat-ui. I havent looked too deep into the codebase but I imagine we will need to refactor the backend endpoints to support assistants API endpoints and then use the openai client to make the requests.

I am more than open to suggestions, and I look forward to exploring how we could collab!

@julien-c
Copy link
Member

would love to support and IMO should be reasonably easy as we're already quite compatible. Let's tag with good first issue Good for newcomers ?

@nsarrazin nsarrazin added enhancement New feature or request good first issue Good for newcomers back This issue is related to the Svelte backend or the DB labels Feb 19, 2024
@CakeCrusher
Copy link
Author

@julien-c
Shifting to the Messages API should be simple but I was moreso thinking of offsetting the responsibility of the conversation storage to an open-source Assistants API (I am currently working on one on FastAPI here https://github.com/OpenGPTs-platform/assistants-api ).

One of the major challenges to this refactor is that in general OS Assistants APIs generally use Postgres (sql) as the entities already have a clear and defined structure and it leaves the door open to deep references. This is to say a migration from Mongo to Postgres may be needed. I am not entirely opposed to reworking the OS Assistants API to work with Mongo but the collection structures would need to be reworked anyways.

@CakeCrusher
Copy link
Author

CakeCrusher commented May 23, 2024

(Im getting back into it now)
Running list of issues addressable out of the box by assistants API:
#1159
#1115

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
back This issue is related to the Svelte backend or the DB enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

3 participants