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
[Feature Request]: Integration of the Latest GPT Model Released on 04.09 version #4573
Labels
enhancement
New feature or request
Comments
The latest GPT model released by OpenAI on April 29 ? Today is April 26. You mean gpt-4-turbo-20240409 ? |
f1h0
changed the title
[Feature Request]: Integration of the Latest GPT Model Released on April 29
[Feature Request]: Integration of the Latest GPT Model Released on March 29
Apr 26, 2024
f1h0
changed the title
[Feature Request]: Integration of the Latest GPT Model Released on March 29
[Feature Request]: Integration of the Latest GPT Model Released on 04.09 version
Apr 26, 2024
04.09 fixed it. I've been working hard for days. and very tired and lost in thought. |
@f1h0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem Description
Staying up-to-date with the latest advancements in AI is crucial for providing users with the best possible experience. NexChat currently does not support the latest GPT model released by OpenAI on 04.09
Solution Description
I propose that NexChat integrates the latest GPT model as soon as possible to leverage improved language understanding and generation capabilities. This update will ensure that users benefit from the most recent enhancements in AI technology for their conversations and inquiries.
Alternatives Considered
While waiting for integration, an interim solution could be to provide users with information on when they might expect the new model to be available on NexChat.
Additional Context
The prompt release of updates following new model releases by OpenAI is crucial for maintaining user trust and satisfaction with NexChat's service quality.
The text was updated successfully, but these errors were encountered: