karthink
karthink
Are you still experiencing this issue?
@tommaisey let me know if you're still experiencing this problem.
@tarsius thank you for the detailed, informative and thoughtful response! ----- #### Persisting transient options I tried both methods, and while neither one is ideal, I can work with these...
> There are also many open questions. For example, should we allow per-package and/or per-menu customization? Should individual prefixes be able to override the user preference, if it would be...
1. Run `(setq gptel-log-level 'debug)` 2. Try to use gptel 3. When you get an error, check the `*gptel-log*` buffer. 4. **Scrub your API key from this buffer** and paste...
It looks like no response is being received at all. Can you run that curl command in the log from the log output in a terminal and check if it...
> It looks like no response is being received at all. Can you run that curl command in the log from the log output in a terminal and check if...
@alx Your issue is different, you get a HTTP 400 error. It's not a silent failure like the others are experiencing. Moreover it fails for you from both the command...
@alx There shouldn't be a newline (`\n`) in your auth token: ``` { "Content-Type": "application/json", "Authorization": "Bearer sk-....\n" } ```
@sonofjon Thanks for the details. It looks like the Curl command fails silently even when you run it at the terminal, so that's the problem. 1. My best guess is...