Update getErrors (GetErrors / problems) tool

[m4dc4p]

Update this tool so it can gather all errors.

• Updated model description so agent knows the tool can gather all errors
• Updated implementation such that if no URL is given, the tool returns all errors.

Fixes microsoft/vscode#260675

[m4dc4p]

@microsoft-github-policy-service agree

[m4dc4p]

This is for microsoft/vscode#257837. If anyone can give me guidance on how to test this locally (that is, install the updated extension in my VS code so the updated tool description is accessible to Copilot) I'd really appreciate it. Guidance on how to best implement this feature also welcome!

[connor4312]

cc @roblourens

[roblourens]

If filePaths is optional, make sure it's also optional in IGetErrorsParams and the tool is implemented accordingly

[roblourens]

See the build errors

[m4dc4p]

Thanks @roblourens for your attention! I updated the interface, and realized I had not really restructed invoke correctly. Now it handles lack of filePaths vs any array properly.

The prepareInvoke function also needed to be updated so it wouldn't throw an error if no paths were given.

[m4dc4p]

BTW can you tell me how to install this into my local VS code so I can test it with copilot? I still don't know if the LLM will understand how to use this new tool definition.

[roblourens]

You should be able to just debug the extension normally to run it https://github.com/microsoft/vscode-copilot-chat/blob/main/CONTRIBUTING.md#developing

[m4dc4p]

I didn't have any luck running the extension (maybe due to use latest main?). In any case this about all the effort I'm able to give right now.

[roblourens]

Can you share the trouble you had running the extension? I want it to be a good experience for external contributors.

You may need to use VS Code Insiders, not the stable release, maybe that's the issue

[m4dc4p]

Can you share the trouble you had running the extension? I want it to be a good experience for external contributors.

No problem! I am using Insiders; I usually write Haskell so running & debugging an extension is a little new. I didn't understand the "Launch Copilot Extension - Watch Mode" from CONTRIBUTING.md, but F5 did start the extension for me.

When I open VS Code ("[Extension Development Host]" is in title bar, so I know its the version I launched), the copilot tab has no models for me to select. When I submit a message, I just get an endless spinner.

Some screenshots to illustrate:

VS Code Version	VS Code ("[Extension Development Host]") Version	Copilot Input	(lack of) Chat Response	Extension Version

I am running based on 60bbbc7 of the copilot extension.

3791ec9 (HEAD -> 257837-update-get-tools, m4dc4p/257837-update-get-tools) Merge remote-tracking branch 'm4dc4p/257837-update-get-tools' into 257837-update-get-tools
5b21add Updates from review
60bbbc7 Merge branch 'main' into 257837-update-get-tools
8c49dc9 Fixes microsoft/vscode#258501 (#421)
7a0177d Fix issue with internal api key reference (#431)

Let me know if I can provide more! Happy to try something different.

[roblourens]

Interesting- I'm assuming that it didn't get built properly or is missing an npm install or something. If you check the debug console (in the initial window), or the Copilot Chat output channel (in the debuggee), you may see a clue.

[roblourens]

In order to merge this, I need to fix this task, which is currently not working on PRs from forks...

[m4dc4p]

@roblourens Thanks for your help with this! Excited to see it land!