GitHub Copilot in VS Code Crashes With Large Workspaces: Fix

A large workspace can expose performance problems in VS Code, but file count alone does not prove that GitHub Copilot caused a crash. Identify the busy or failing process, isolate extensions, and reduce irrelevant search/index content. Keep source files and database dumps intact while testing.

Official documentation checked October 14, 2026. No fixed RAM requirement, crash threshold, or percentage improvement is guaranteed by the guidance below.

Why Copilot Can Appear to Crash in Large Workspaces

VS Code runs multiple processes. Extensions, language servers, file watching, Git operations, and other editor activity can contribute to load. An extension-host crash does not identify Copilot as its cause, and an extension bug remains possible. Compare the same reproduction steps with and without the relevant feature instead of assuming that 500 files exceed a universal memory limit.

Copilot’s workspace context is feature-specific. Current VS Code documentation describes local or remote semantic indexes, searches, and editor context. It does not say every file is loaded into memory whenever a folder opens. Ignored and excluded files and binary files have different treatment. See how Copilot understands a workspace.

Record the versions, operating system, whether you use WSL/SSH/a container, the operation that triggers the issue, and the time it occurs. A remote extension host and the local editor can have different bottlenecks. This makes the next test useful and gives a support report enough context.

Steps to Diagnose and Reduce Workspace Load

1. Find the Process and Extension

Save your work, update through approved controls, and reproduce once with Help > Open Process Explorer visible. Use Developer: Show Running Extensions for extension activity. The VS Code performance guide explains how to collect a profile when an extension host is busy.

Temporarily disable the suspected extension through the Extensions view, repeat the same action, then restore it. Use Help: Start Extension Bisect when the culprit is unclear. If Copilot is disabled during a test, its missing suggestions are expected; test whether the editor freeze or host crash persists.

2. Exclude Irrelevant Search and Index Content

Back up or version your workspace settings and review existing patterns before adding any. The official workspace-context guide distinguishes files.exclude, which hides files and excludes them from searches and the semantic index, from search.exclude, which excludes search/grep results while keeping files visible. For example, merge suitable generated-output patterns into the existing settings object:

{
  "search.exclude": {
    "**/node_modules/**": true,
    "**/dist/**": true,
    "**/coverage/**": true
  }
}

This example narrows search results; it is not a guarantee that every Copilot feature will avoid those files. Decide separately whether generated content should be hidden with files.exclude or ignored by Git. An ignored file that you open or select can still provide context. These settings are not a confidentiality boundary or a replacement for organization content policies.

Do not use git.ignoredRepos as a Copilot exclusion switch. Git integration settings are not the documented control for Copilot’s semantic index. Check the index state in the Copilot status dashboard before attributing ongoing work to indexing.

3. Test a Smaller Workspace Without Moving Files

Save the existing workspace and unsaved edits, then open a relevant project subfolder in a new window. For several related folders, use File > Add Folder to Workspace and save the resulting workspace. This changes the editor’s open roots without deleting the files. Confirm that required configuration and shared source remain available; a smaller workspace can affect build tasks and language tooling. See VS Code’s multi-root workspace guide.

If the Workspace Still Freezes or Crashes

• Only inline suggestions trigger the problem: temporarily disable them for the active language in the Copilot status menu. github.copilot.enable controls inline suggestions; it is not a general workspace-index or privacy switch. See the inline-suggestions reference.
• A huge file is involved: close its editor tab and exclude it from the relevant search/index operation where appropriate. Keep the file intact. A 10 MB threshold is not a documented instruction to delete data.
• The failure occurs only remotely: inspect the affected remote process and extension installation as well as local logs.
• Copilot cannot connect: follow Copilot diagnostics. A network failure requires different evidence from an editor resource problem.

Compare Results Before Keeping a Change

Keep a change only when it addresses your measured problem without removing needed context. If the issue remains, report the versions, reproduction steps, affected process, and a redacted profile/log excerpt. Exclusion patterns can reduce unnecessary work, but they cannot guarantee that a large monorepo will never crash.