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.

Sign up for GitHub

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

Jump to bottom

Best practice for developers control over which kernel functions get advertised to the LLM #6154

Open

markwallace-microsoft opened this issue May 8, 2024 · 0 comments

Labels

documentation enhancement

Member

markwallace-microsoft commented May 8, 2024 •

edited

Purpose of this task is to provide some guidance and samples for developers on how control which kernel functions get advertised to the LLM

Some options

Use the tool behaviour which allows the developer specify which functions from the kernel to use.
Provide an option when plugins/functions are registered to mark them as "not for LLM" e.g. if I have functions I only expected to be called when rendering prompts.
Exclude the current function, see .Net: Invoking kernel function directly with auto invoke enabled results in multiple nested calls to the function #6281
Prevent possible loops

markwallace-microsoft added triage enhancement documentation and removed triage labels

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment