Added ToolUser parameter system_prompt and verbosity #20
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What it does and Why
It is very convenient to have support for system prompts even when using function calling. In the current implementation, I couldn't find an easy way to supply a custom system prompt. Hence, I added a parameter for system_prompt on ToolUser, which simply inserts the user-specified system prompt in front of the system prompt generated for function calling. This produces a longer system prompt, but this did not negatively affect the function calling effectiveness of Claude 3 Opus during my personal testing.
For debugging purposes, I also added a verbosity flag that makes it easier to track the final system prompt.