Skip to content

Commit 833d2a6

Browse files
committed
README: Hide authinfo explanation, update Claude 3.7 info
* README.org (Claude 3.7 support, authinfo): Hide authinfo details. This is causing more confusion than clarity as readers are faced with two unfamiliar systems (gptel and authinfo configuration) instead of one. Update the Claude 3.7 thinking support text -- using a separate Anthropic backend for this model is now the official solution, as no Anthropic-only user options are planned for now to set this.
1 parent 7938768 commit 833d2a6

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

README.org

+6-4
Original file line numberDiff line numberDiff line change
@@ -93,7 +93,6 @@ gptel uses Curl if available, but falls back to the built-in url-retrieve to wor
9393
- [[#setup][Setup]]
9494
- [[#chatgpt][ChatGPT]]
9595
- [[#other-llm-backends][Other LLM backends]]
96-
- [[#optional-securing-api-keys-with-authinfo][(Optional) Securing API keys with =authinfo=]]
9796
- [[#azure][Azure]]
9897
- [[#gpt4all][GPT4All]]
9998
- [[#ollama][Ollama]]
@@ -214,14 +213,17 @@ Once this backend is registered, you'll see model names prefixed by "Claude:" ap
214213

215214
See below for details on your preferred LLM provider, including local LLMs.
216215

217-
**** (Optional) Securing API keys with =authinfo=
216+
#+html: <details><summary>
217+
***** (Optional) Securing API keys with =authinfo=
218+
#+html: </summary>
218219

219220
You can use Emacs' built-in support for =authinfo= to store API keys required by gptel. Add your API keys to =~/.authinfo=, and leave =gptel-api-key= set to its default. By default, the API endpoint DNS name (e.g. "api.openai.com") is used as HOST and "apikey" as USER.
220221
#+begin_src authinfo
221222
machine api.openai.com login apikey password sk-secret-openai-api-key-goes-here
222223
machine api.anthropic.com login apikey password sk-secret-anthropic-api-key-goes-here
223224
#+end_src
224225

226+
#+html: </details>
225227
#+html: <details><summary>
226228
**** Azure
227229
#+html: </summary>
@@ -534,7 +536,7 @@ The above code makes the backend available to select. If you want it to be the
534536

535537
***** (Optional) Interim support for Claude 3.7 Sonnet
536538

537-
gptel does not yet support specifying LLM "reasoning"/"thinking" behaviors dynamically through its interface. This effort is ongoing, but in the meantime you use the Claude 3.7 Sonnet model in its "thinking" mode by defining a second Claude backend and selecting it in via the UI or elisp:
539+
To use Claude 3.7 Sonnet model in its "thinking" mode, you can define a second Claude backend and select it via the UI or elisp:
538540

539541
#+begin_src emacs-lisp
540542
(gptel-make-anthropic "Claude-thinking" ;Any name you want
@@ -553,7 +555,7 @@ gptel does not yet support specifying LLM "reasoning"/"thinking" behaviors dynam
553555

554556
You can set the reasoning budget tokens and max tokens for this usage via the =:budget_tokens= and =:max_tokens= keys here, respectively.
555557

556-
Once proper support for specifying reasoning behaviors is added to gptel's UI this will be unnecessary.
558+
You can control whether/how the reasoning output is shown via gptel's menu or =gptel-include-reasoning=, see [[#handle-reasoning-content][handling reasoning content]].
557559

558560
#+html: </details>
559561
#+html: <details><summary>

0 commit comments

Comments
 (0)