-
Notifications
You must be signed in to change notification settings - Fork 704
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
How to use with node-llama-cpp for backend #238
Comments
@TimeLordRaps that's awesome, thanks for figuring this out! Would you mind contributing this to our documentation? |
So I'm still currently testing around with this, it might not be fully functional as the LlamaCpp custom Llm form langchain has trouble with tools. Could someone familiar with the matter explain to me where in the code to look to see the downstream effects of failing tool uses. |
@TimeLordRaps at a high level the code lives here and here. But it can be a bit challenging to come in there cold. It's a complex part of the codebase (and will actually get more complex in the near as we repurpose the underlying function calling capability to do more and more..). It might be easiest to test empirically, having 2 identical examples and switching only I actually think this should live more than just in documentation, but in ready-made I'd love to collaborate / pair program with you to help you make this first addition of its kind of you are interested. And I can also help you get oriented with tool calls if you want to dig deeper. btw, cool username |
I'd love the opportunity to pair program an implementation of some contribution to this project. However I'm not sure this issue would be my first choice. I'll reach out on discord though. |
This would make a great first issue: Add the code to the langchain docs to explain how to use other LLMs. |
Documentation description
Just a relevant example of how to use with node-llama-cpp
Steps include installing node-llama-cpp
installing langchain/community
and here's relevant code:
Relevant Context
Where this documentation fits in
The text was updated successfully, but these errors were encountered: