-
Notifications
You must be signed in to change notification settings - Fork 150
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
Add o1-preview support (or how to hack it in) #393
Labels
enhancement
New feature or request
Comments
There is an open PR to allow disabling the system message, see #339. |
For those who are willing to try hack, I see it's working with this changes. |
I did exactly what @ileixe suggested above, with adjustments for the breaking changes: # git diff HEAD^1
diff --git a/gptel-openai.el b/gptel-openai.el
index 61339b3..a4ac6ef 100644
--- a/gptel-openai.el
+++ b/gptel-openai.el
@@ -181,7 +181,8 @@ with differing settings.")
:content
(gptel--trim-prefixes (buffer-substring-no-properties (point-min) (point-max))))
prompts))
- (cons (list :role "system"
+ ;; (cons (list :role "system"
+ (cons (list :role "user"
:content gptel--system-message)
prompts))) Additionally, my (setq
gptel-model 'o1-mini
gptel-backend (gptel-make-openai
"ChatGPT"
:key 'gptel-api-key
:stream nil ;; server doesn't accept stream = true with o1-mini
:models '((gpt-3.5-turbo) (gpt-3.5-turbo-16k) (gpt-4o-mini)
(gpt-4) (gpt-4o) (gpt-4-turbo) (gpt-4-turbo-preview)
(gpt-4-32k) (gpt-4-1106-preview) (gpt-4-0125-preview)
(o1-preview) (o1-mini)))) And that's it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, I can't do
The problem I am running into so far is that o1-preview does not support system messages yet. And it seems gptel always tries to send system messages. Could there be an option not to send a system message (or what is the option if it exists)?
Alternatively, how can I hack it so that it works? Some pointers would be helpful.
The text was updated successfully, but these errors were encountered: