Replies: 3 comments 6 replies
-
Please see the section of the README that explains how to store secrets in authinfo in a way that will work with You can also just ignore all of that and provide the key yourself, in whatever way works for you. Using authinfo is only a suggestion. I use GNU pass myself to store these API keys. |
Beta Was this translation helpful? Give feedback.
-
I found the issue. I thought the gptel-backend (gptel-make-gemini "Gemini"
:key (gptel-api-key-from-auth-source "generativelanguage.googleapis.com")
:stream t) However, it turns out it cannot find the key properly. I don't know the detail in the It seems that I had the wrong configuration of it. So, resolution for me is (setq gptel-backend (gptel-make-gemini "Gemini"
:host "generativelanguage.googleapis.com"
:key gptel-api-key
:stream t
:request-params nil :curl-args nil) |
Beta Was this translation helpful? Give feedback.
-
Thinking this again, I'm not sure why the initial configuration as gptel-backend (gptel-make-gemini "Gemini"
:key (gptel-api-key-from-auth-source "generativelanguage.googleapis.com")
:stream t) was working with Do you have any idea? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm using gemini and the key is in the
.authinfo.gpg
However,
gptel-make-gemini
cannot read the key from the gpg file.If there is plain text of .authinfo, then it reads well.
Is there a way to read the .authinfo.gpg? for filling the apikey?
Beta Was this translation helpful? Give feedback.
All reactions