Re:Ollama releases OpenAI API compatibility
by swyx on Thursday February 08, 2024 @06:34PM
(#39309300)
and disappear at any time... was a leetle bit unsettled by the sudden deprecation of "functions" for "tools" with only minor apparante benefit
Re:Ollama releases OpenAI API compatibility
by nl on Thursday February 08, 2024 @06:51PM
(#39309444)
and what does `auto` even mean?
Re:Ollama releases OpenAI API compatibility
by athyuttamre on Friday February 09, 2024 @05:56AM
(#39313572)
Hey nl — I work at OpenAI on our API. Do you mean `tool_choice="auto"`? If so, it means the model gets to pick which tool to call. The other options are:
- `tool_choice={type: "function", function: {name: "getWeather"}}`, where the developer can force a specific tool to be called. - `tool_choice="none"`, where the developer can force the model to address the user, rather than call a tool.
If you have any other feedback, please feel free to email me at [email protected]. Thanks!
Re:Ollama releases OpenAI API compatibility
by athyuttamre on Friday February 09, 2024 @05:55AM
(#39313561)
Hey swyx — I work at OpenAI on our API. Sorry the change was surprising, we definitely didn't do a great job communicating it.
To confirm, the `functions` parameter will continue to be supported.
We renamed `functions` to `tools` to better align with the naming across our products (Assistants, ChatGPT), where we support other tools like `code_interpreter` and `retrieval` in addition to `function`s.
If you have any other feedback for us, please feel free to email me at [email protected]. Thanks!
Re:Ollama releases OpenAI API compatibility
by londons_explore on Friday February 09, 2024 @06:03AM
(#39313613)
Might be a good idea to have API versions for this... Then when someone builds a product against "version 1", they can be sure that new features might be added to version 1, but no fields will be removed/renamed without openai releasing version 2.
To consume them, just assume that every field is optional and extra fields might appear at any time.