You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, sorry if the title isn't the best, I just couldn't think of something better.
The problem I have is that I'm trying out several models, and each one works best with a different prompt. Especially those that are specifically made for a task, like *-code models. Therefore, templates should be way more versatile and customizable.
I was thinking that it would be great if, when defining a new provider, one could set the templates. Something like
(setopt ellama-providers
'(("zephyr". (make-llm-ollama
:chat-model"zephyr:7b-beta-q6_K":embedding-model"zephyr:7b-beta-q6_K"))
...
:templates
((code-completion ."Complete the following code in a single markdown block: %s")
(etc...))))
This + what was discussed on #110 + maybe a system to detect whether a model in installed or not would make ellama way better to set up (probably this part should be another issue)
I can contribute, but I'm still getting the FSF copyright assignment (+ I'm not the best elisper out there)
The text was updated successfully, but these errors were encountered:
Hello, sorry if the title isn't the best, I just couldn't think of something better.
The problem I have is that I'm trying out several models, and each one works best with a different prompt. Especially those that are specifically made for a task, like *-code models. Therefore, templates should be way more versatile and customizable.
I was thinking that it would be great if, when defining a new provider, one could set the templates. Something like
This + what was discussed on #110 + maybe a system to detect whether a model in installed or not would make ellama way better to set up (probably this part should be another issue)
I can contribute, but I'm still getting the FSF copyright assignment (+ I'm not the best elisper out there)
The text was updated successfully, but these errors were encountered: