Repository navigation
Using multiple chat services in one Kernel for different skills #1926
Replies: 3 comments
|
I am also encountering this issue. Using the kernel.set_default_chat_service() before calling semantic functions does not work either. |
0 replies
|
If anyone else ever runs into this, setting the default chat service actually ended up working. In my previous comment I was:
What ended up working was using |
0 replies
|
I still think it would be nice to have a param or config option for each skill to indicate the service preference |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Maybe I'm doing something wrong, but it doesn't seem to work in the Python version reading the "default_backends" key for skills.
No matter what values I put there, the default chat service is still used.
In the tests and documentation I did not find examples of using different services for different skills
All reactions