VS Code completion stops working when application is running

I’ve set up GitHub Copilot for business in Visual Studio, and I’m noticing something strange. The code suggestions appear perfectly when I’m not running my application. However, when I start debugging or run the project, the suggestions completely vanish. It feels like Copilot stops working during debugging. Has anyone faced a similar problem? I’d like to know if there’s a specific setting I need to adjust or if this is just how Copilot functions. It would be greatly beneficial to have suggestions available while I’m testing and making adjustments.

This behavior is actually quite common with GitHub Copilot in VS Code during active debugging sessions. In my experience, the issue stems from how VS Code prioritizes processes when the debugger is running. The IDE essentially puts non-critical extensions on hold to ensure smooth debugging performance. I found that adjusting the github.copilot.enable setting to force it to remain active helped, though you might notice some performance impact. Another workaround I discovered was switching to the integrated terminal for running applications instead of using the full debugger when you just need to test functionality. The suggestions typically return immediately once you stop the debugging session. It’s an annoying limitation but seems to be by design rather than a bug.

totally get what u mean, its pretty frustrating. have u checked if copilot is active in the extensions while debugging? sometimes it turns off by itself. and watch out for breakpoints, they can mess with it too.

I experienced this exact issue a few months back and it drove me crazy for weeks. The problem turned out to be related to VS Code’s resource allocation during debugging sessions. When the debugger is active, it consumes significant system resources and can cause extensions like Copilot to throttle or temporarily disable themselves to maintain performance. What worked for me was increasing the editor’s memory limit through the settings and also making sure I had enough RAM available. You might also want to check if you have any conflicting extensions running simultaneously during debug mode. Another thing to try is restarting the Copilot service while debugging by using the command palette and running the GitHub Copilot restart command.