3 ms·
and disappear at any time... was a leetle bit unsettled by the sudden deprecation of "functions" for "tools" with only minor apparante benefit
by swyx 3y ago
and disappear at any time... was a leetle bit unsettled by the sudden deprecation of "functions" for "tools" with only minor apparante benefit
- nl 3y agoand what does `auto` even mean?
- athyuttamre 3y agoHey 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 atty@openai.com. Thanks!
- athyuttamre 3y agoHey 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 atty@openai.com. Thanks!
- londons_explore 3y agoMight 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.