fix: JSON schema issue with gemini tool calls#3851
Conversation
✅ Deploy Preview for continuedev ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
Note, have pulled branch and tested, works great. |
|
Hi @monotykamary, yesterday we shared some updates with our contributors about how we're aiming to improve the contribution process. Part of this included the addition of a Contributor License Agreement (CLA) to protect both contributors and the project. We're reaching out to ask that previous contributors sign it. Could you please take a moment to sign, or if you have any questions send me a message? (either here or nate@continue.dev would work) To do so, you just need to post a comment below with the following text: ❤️ Thank you for the work you've done on Continue, and let me know if you have any suggestions on how we can make the project even better! |
|
All contributors have signed the CLA ✍️ ✅ |
|
I have read the CLA Document and I hereby sign the CLA |
Description
Fixes tool calling error that happens when using Gemini. Not actually sure if it's because of MCP servers, but at least now it works.
Checklist
Screenshots
Testing instructions
Select any Gemini model and enable tools. Prompt it in such a way that it will invoke the tool and see the results.