Why GitHub Copilot Suggestions Are Empty in VS Code Insiders

You open VS Code Insiders, start typing code, and GitHub Copilot shows no suggestions. The Copilot icon in the status bar is grayed out or shows an error. This problem often occurs because the Insiders build uses a different extension registration path or a separate authentication token than the stable release. This article explains the root causes of empty Copilot suggestions in VS Code Insiders and provides the exact steps to restore inline completions.

Why Copilot Stops Suggesting Code in VS Code Insiders

VS Code Insiders is a nightly preview build that runs alongside the stable release. Each build stores its extensions, settings, and authentication data in separate directories. If you installed GitHub Copilot on the stable release, it does not automatically appear in the Insiders build. The Copilot extension must be installed again inside the Insiders environment.

A second common cause is a missing or expired GitHub authentication token. Copilot requires a valid token tied to your GitHub account. If you signed in on the stable build, that token is not transferred to Insiders. The Insiders build shows an empty suggestion list because the extension cannot verify your subscription status.

A third cause involves Settings Sync. If you enabled Settings Sync on the stable release and then signed into the same account on Insiders, the synced settings may have disabled the Copilot extension or turned off inline suggestions. The Insiders build inherits these settings silently, leaving you with no visible error but no completions either.

Steps to Restore Copilot Suggestions in VS Code Insiders

1. Install the Copilot extension in Insiders
   Open VS Code Insiders. Press Ctrl+Shift+X to open the Extensions view. Search for “GitHub Copilot”. Click the Install button next to the official extension by GitHub. Wait for the installation to finish. Restart the Insiders window.
2. Sign in to GitHub from the Insiders build
   Click the Copilot icon in the status bar at the bottom right. Select “Sign in to GitHub”. A browser tab opens asking you to authorize VS Code Insiders. Complete the authorization. Return to VS Code Insiders. The status bar icon should turn solid to indicate active authentication.
3. Check the Copilot extension settings
   Open the Command Palette with Ctrl+Shift+P. Type “Preferences: Open Settings (UI)”. Search for “Copilot: Enable”. Make sure the checkbox is checked. Search for “Editor: Inline Suggest” and confirm it is enabled. If either setting is off, turn it on and restart Insiders.
4. Disable and re-enable the extension
   In the Extensions view, find GitHub Copilot. Click the gear icon and select “Disable”. Reload the window. Then enable the extension again. This clears any corrupted extension state.
5. Clear the Insiders extension cache
   Close VS Code Insiders completely. Open File Explorer and navigate to %USERPROFILE%\.vscode-insiders\extensions. Delete the folder named github.copilot-. Also delete github.copilot-chat- if it exists. Reopen VS Code Insiders and reinstall the extension from step 1.
6. Reset Settings Sync for Insiders
   Open the Command Palette. Type “Preferences: Turn off Settings Sync”. Confirm the action. Then sign into Settings Sync again using the same GitHub account. Choose to apply settings from a fresh profile, not from the stable release. This prevents the stable release settings from disabling Copilot in Insiders.

If Copilot Still Has Issues After the Main Fix

Copilot shows “Sign in to use Copilot” after every restart

This indicates the authentication token is not persisting. Open the Command Palette, type “Developer: Toggle Developer Tools”, and check the Console tab for token-related errors. A common fix is to revoke the old VS Code Insiders token in your GitHub account under Settings > Applications > Authorized OAuth Apps. Then repeat step 2 from the main fix section.

Copilot suggestions appear but are irrelevant or incomplete

This is usually a language server issue. Open the Command Palette and run “Developer: Reload Window with Extensions Disabled”. Then enable only the Copilot extension. If the suggestions improve, another extension is interfering. Disable extensions one by one to find the conflict.

Copilot icon stays gray even after signing in

The extension may be waiting for a license check. Open the Output panel by pressing Ctrl+Shift+U. Select “GitHub Copilot” from the dropdown in the panel. Look for lines that say “Error fetching user profile” or “Token expired”. If you see an error, sign out of GitHub in the status bar and sign back in. If the problem persists, check your GitHub Copilot subscription status at github.com/settings/copilot.

Item	VS Code Stable	VS Code Insiders
Extension install path	%USERPROFILE%\.vscode\extensions	%USERPROFILE%\.vscode-insiders\extensions
Authentication token	Stored in stable build keychain	Stored in Insiders keychain separately
Settings Sync profile	Uses stable release profile	Uses Insiders profile unless synced from stable
Copilot extension version	Stable release channel	Insiders release channel

VS Code Insiders treats extensions, authentication, and settings as completely separate from the stable build. You must install Copilot, sign in, and configure settings inside the Insiders environment. The table above shows the key differences that cause empty suggestions when these components are not set up correctly.

You can now restore GitHub Copilot suggestions in VS Code Insiders by reinstalling the extension, signing in with your GitHub account, and verifying the extension settings. After completing the steps, test Copilot by typing a comment like // function to calculate and pressing Enter. The inline suggestion should appear within one second. If you switch between stable and Insiders builds frequently, consider disabling Settings Sync for the Copilot extension to avoid future conflicts.