Add Run Options. Fixes #7. #8
Merged
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.
A Run can be created using several useful options.
https://platform.openai.com/docs/api-reference/runs
I'm not seeing a lot of value in overriding things that seem to warrant a new Assistant/Tool within our framework. For example, assistant_id, model, instructions, tools, temperature, top_p, response_format, etc. Let me know if y'all disagree.
That said, options like
tool_choiceto force function call(s) or even others such asadditional_instructions, andadditional_messagesall seem to make sense. I have a use case now where I would like to force function calls for some expert Tool(s). Will consider how to address this.