Commit abb0bff
committed
Stop listing Gemini as an OpenAI-compatible provider
The provider roster, both pointers on the OpenAI page and the Functions guide all named Google Gemini as an example of a provider that speaks the OpenAI Chat Completions protocol. Its tool calling does not, so the recommendation sends people at an endpoint that returns blank replies as soon as a tool is involved.
The Functions guide was the worst of the four: it told Gemini users they do not need a Function, when a pipe calling Google's own API is one of the working answers.
The Gemini tab in the OpenAI-compatible guide stays, since people will connect it regardless and that tab is where the limitation is now documented.1 parent 51a5fe4 commit abb0bff
3 files changed
Lines changed: 4 additions & 4 deletions
File tree
- docs/getting-started/quick-start/connect-a-provider
Lines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
48 | 48 | | |
49 | 49 | | |
50 | 50 | | |
51 | | - | |
| 51 | + | |
52 | 52 | | |
53 | 53 | | |
54 | 54 | | |
| |||
Lines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
10 | 10 | | |
11 | 11 | | |
12 | 12 | | |
13 | | - | |
| 13 | + | |
14 | 14 | | |
15 | 15 | | |
16 | 16 | | |
| |||
Lines changed: 2 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
8 | 8 | | |
9 | 9 | | |
10 | 10 | | |
11 | | - | |
| 11 | + | |
12 | 12 | | |
13 | 13 | | |
14 | 14 | | |
| |||
107 | 107 | | |
108 | 108 | | |
109 | 109 | | |
110 | | - | |
| 110 | + | |
111 | 111 | | |
112 | 112 | | |
113 | 113 | | |
| |||
0 commit comments