@problems
and Sixth can see every diagnostic issue VSCode has detected.
When you type @
in chat, select “Problems” from the menu or just type @problems
directly. Sixth will immediately see all the errors and warnings from your workspace, complete with file locations and error messages.
I use the problems mention constantly when I’m stuck on build errors or TypeScript issues. Instead of trying to describe the errors or copy them one by one, I just ask:
@problems
instead of copying error messages. You’ll get more accurate help because Sixth can see the complete error context and locations.
@problems
pattern in your textvscode.languages.getDiagnostics()
API to get all errors and warnings