Adding o1 model and updating endpoint usage
#64
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request includes several changes to the
core/js/gpt-core.js,core/js/options.js, andindex.htmlfiles. The changes primarily focus on updating token-related parameters and adding support for a new model.Updates to token parameters:
core/js/gpt-core.js: Changedmax_tokenstomax_completion_tokensin multiple instances to better reflect the intended parameter usage. [1] [2] [3]Model and message role updates:
core/js/gpt-core.js: Updated the initial message role from 'system' to 'developer' to better align with the context of the messages.core/js/options.js: Added support for the new modelo1in various functions to ensure it is correctly handled. [1] [2] [3]index.html: Added the new modelo1to the dropdown options in the HTML file.