GitHub Copilot freezes VS Code? Fix Copilot Chat lag and lockups (2026)
Quick answer: When GitHub Copilot freezes VS Code or Copilot Chat takes many seconds to respond, the usual causes are a heavy workspace context scan on each message, an extension/VS Code regression, or model-routing overhead—not “your code is too big” alone. Pinning extension versions, shrinking open tabs/workspace scope, and clearing chat history often help immediately; details are below.
The problem: Copilot freezes VS Code for many users
Since early March 2026, developers across Reddit, the VS Code issue tracker, and X have reported the same thing: GitHub Copilot Chat can take 5–20 seconds to acknowledge a message in affected environments. Pasting code into Chat can also stall for several seconds, and some users report temporary lockups. This pattern appears in public VS Code issues like #299738, #300136, and #299786.
Separately, Copilot plan/model behavior has evolved in 2026 (including wider use of Auto model selection and plan-specific model access). Instead of assuming old model-selection rules, verify your current plan behavior in GitHub docs before troubleshooting model-routing issues.
Likely causes (what engineers report)
In affected setups, delays often line up with the Copilot Chat pipeline: context preparation, token estimation, and server round-trips before the main model run. Commenters on the issues linked above also point to extra pre-model calls (for example small “progress” requests) adding wall-clock time. When that stack is slow—large workspace, many open files, remote SSH, or a cold extension host—you can see multi-second hangs on send or paste. Treat this as a working theory for troubleshooting, not a single confirmed root cause for every machine.
Auto model selection can compound the issue in some workflows: routing may change by plan, model availability, and system conditions. If responses degrade, check the model selected per response and compare with manual model choice where available.
Workarounds (what helps right now)
- Pin your VS Code and Copilot extension versions. Roll back to the last version that worked for you (pre-March update). In VS Code, right-click the Copilot extension → “Install Another Version.”
- Close unused tabs and reduce workspace size. The context scanner slows down proportionally with open files. Keep 3–5 relevant files open, not 30.
- Review telemetry- and diagnostics-related settings. Some threads suggest Copilot Chat telemetry or diagnostics paths add overhead; if you experiment, change one setting at a time and confirm in release notes whether a key still exists in your VS Code/Copilot versions.
- Clear workspace chat history frequently. Context window overflow causes erratic behavior including overwriting unrelated files and deleting random code chunks. Start fresh chats for each task.
The deeper fix: stop depending on Chat for complex work
Even when Copilot Chat works at full speed, chat is still scoped differently than a full-repo agent: it may not carry the same cross-file context your team relies on, so suggestions can miss conventions, architecture, and shared types. Published acceptance-rate numbers vary widely by study, language, and task—use your own edit logs and review burden as the ground truth, not a single benchmark.
The pattern that actually saves time: write a short spec before you prompt any AI tool. Define what you’re building, which files are involved, and what “done” looks like. The tool I use for this is BrainGrid—it’s built for Cursor and Claude Code users who want structured task specs that feed directly into Agent mode. Instead of re-prompting a broken Chat 5 times, you prompt once with a clear spec and get the right output.
Our take
Copilot works well for single-file autocompletion and boilerplate. For larger multi-file tasks, reliability and speed can vary by extension version, IDE build, and environment (especially remote setups). If you’re spending more time waiting on Chat than writing code, it may be worth testing alternate workflows and tools with stronger whole-codebase context.
Stop waiting on broken Chat. Spec your tasks before you prompt and get the right output in one round. Try BrainGrid →
BrainGrid helps Cursor and Claude Code users structure specs so agents often need fewer back-and-forth rounds—which can mean fewer credits burned and cleaner output for many workflows.