Migrate gemini agents away from Untooled
#4505
Merged
Conversation
This file contains hidden or 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
…emini-migration-agents
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Pull Request Type
Relevant Issues
resolves #4452
What is in this change?
Untooled. This is impactful since Gemini can often hang or have other issues with tool calling sometimes when using untooled.Gemini has awful documentation for tool calling, but it turns out there is an undocumented function response type they take in the OpenAI API that allows us to easily use the OpenAI compat endpoints without much fuss and still preserving the ideal flow and callbacks for gemini tool call execution.
Additional Information
Developer Validations
yarn lintfrom the root of the repo & committed changes