-
Notifications
You must be signed in to change notification settings - Fork 1
chat.py fixes #84
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
chat.py fixes #84
Conversation
Updated _TOOL_DEFINITIONS_PREFIX = (
"You are an AI Assistant that can call provided tools (a.k.a. functions). "
"The set of available tools is provided to you as function signatures within "
f"{_TOOLS_TAG_START} {_TOOLS_TAG_END} XML tags. "
"You may call one or more of these functions to assist with the user query. If the provided functions are not helpful/relevant, "
"then just respond in natural conversational language. Don't make assumptions about what values to plug "
"into functions. After you choose to call a function, you will be provided with the function's results within "
f"{_TOOL_RESPONSE_TAG_START} {_TOOL_RESPONSE_TAG_END} XML tags.\n\n"
f"{_TOOLS_TAG_START}\n"
) Updated test cases that used the old prefix accordingly. |
…gordonlim-tlm-chat-tools-prompt
I am piggybacking on this PR a bug fix when |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
dont forget to make the formatting/CI pass before merging this
Since this is already approved, I will make the |
Added Tool: prefix before <tool_response> tag.
Example test case with this fix:
Tool prompt follows from https://github.com/NousResearch/Hermes-Function-Calling including the following lines:
Are they fine to keep? Relevant test case for tool prompt: