New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question about OpenAILike usage #137
Comments
Hello! Since many providers use |
Thanks @antonsapt4, as @ysolanky pointed out Groq doesnt support tools yet. As soon as they do we should have that available as well :) |
Thanks @ysolanky @ashpreetbedi. Yes just read on groq website that the endpoint is not supported function calling. After playing around, looks like only Ollama with openhermes model that can do tools calling, do you know what local model that can use the tools / function calling? LM Studio even tho using the same OpenHermes (https://huggingface.co/TheBloke/OpenHermes-2.5-Mistral-7B-GGUF) looks like still cannot call tools using the code above. Really appreciate if anyone had any experience using different model beside Ollama OpenHermes to have comparison. |
@antonsapt4 sadly currently we've only seen openhermes to be decent-ish at tool calling. We're still very early in the function calling journey, even so much that most LLM providers dont support it yet. We'll see this become mainstream in the next few months and you'll get more models/LLM providers supporting it |
@antonsapt4 try out hermes2 for function calling, it is very very good for a 7b model: https://github.com/phidatahq/phidata/tree/main/cookbook/hermes2 |
Saw this LM-Studio Cookbook,
Is it because LM-Studio OpenAI API provided is supporting tools?
Since I'm using colab wondering how
OpenAILike
works and tried with Groq endpointllm=OpenAILike(base_url="https://api.groq.com/openai/v1", api_key="gsk_xxxxxx", model="mixtral-8x7b-32768"),
it said:
tools
is not supported with this model. Just want to get my head around it.And kudos with phi-data it really make opensource model usable in very clear way without many workaround!
The text was updated successfully, but these errors were encountered: