Our integration does support native tool calling in the VS LM API - seems to work in the models I've tested at least. Which models aren't working for you?
Can you please open an issue with more details like the VS Code version you have and the names of the models that you've tried and the exact errors you're seeing? I'll keep an eye out for it.
Great change!
Jerk move to screw local users . bye bye Roo
The problem is, some organizations can only use VS LM API, which only support XML only.
This force us to stay in older version of RooCode. Did you think about this ?
Our integration does support native tool calling in the VS LM API - seems to work in the models I've tested at least. Which models aren't working for you?
Thanks for looking into this - Sorry that I should raise issue but there are too many and unable to get attention..
From my testing:
Any model selected was failing from v3.36.11.
Version between 3.36.11 - 3.36.16 were working only when selects protocol as XML manual, instead of default.
Check the LM API version in Copilot chat:
"The VS Code Language Model (LM) API is currently at version 1 (vscode.lm.v1).
This API was introduced in VS Code version 1.90 (May 2024) and provides access to language models for extensions."
I am not sure if it related to versio of copilot deployed in the organization but it's out of our control.
Can you please open an issue with more details like the VS Code version you have and the names of the models that you've tried and the exact errors you're seeing? I'll keep an eye out for it.
This is really awesome. Without this update, there’s no way my team and I would’ve moved from Roo Code to Claude Code.