VSCode copilot debug is great

Dawid Laszuk published on
1 min, 174 words

Just as I was getting tired of all these incorrect suggestions by the Github Copilot, I learned about its copilot-debug option (link). When executing something in the (VSCode built-in) terminal, if you append copilot-debug to its name, it'll try to figure out vscode setting for debugging. It can take a while to get the proper VSCode launch.json config, but once it's there, you can just save it. They also provide a nice prompt asking what you want to do with the output (of the debug config).

I'm not sure how it works on more complicated setups. Likely, not great, as with most LLMs on more convoluted questions, but I don't recommend anyone rely on it for difficult tasks (yet). Anyway, it came in handy today. I hope I won't forget about it the next time I want to debug something.

Here's release note for the feature: https://code.visualstudio.com/updates/v1_96#_debugging-with-copilot