Why GitHub Copilot Sidebar Won’t Open in VS Code

You installed the GitHub Copilot extension in Visual Studio Code, but the sidebar panel does not appear when you click the Copilot icon. The Copilot icon may remain dimmed, or clicking it produces no response. This problem typically occurs due to extension conflicts, corrupted extension cache, or incorrect VS Code settings that block the sidebar from loading. This article explains the three most common root causes and provides step-by-step fixes to restore the Copilot sidebar.

Why the Copilot Sidebar Fails to Load

The GitHub Copilot sidebar is a webview panel rendered inside VS Code. When the panel fails to open, the root cause is almost always one of three scenarios: a conflict with another installed extension, a corrupted local cache for the Copilot extension, or a VS Code setting that prevents the sidebar from rendering. Understanding these causes helps you apply the correct fix without disabling unrelated extensions or reinstalling VS Code.

Extension Conflicts

VS Code extensions run in a shared extension host process. If another extension modifies the same UI components or webview resources, the Copilot sidebar may fail to initialize. Common culprits include theme extensions that override webview styles, keybinding extensions that reassign the Copilot shortcut, and older versions of the GitHub Pull Requests extension.

Corrupted Extension Cache

The Copilot extension stores authentication tokens, model configuration, and UI state in a local cache folder. If this cache becomes corrupted due to an incomplete update or a disk write error, the sidebar cannot load its initial content. The icon appears in the activity bar, but clicking it does nothing.

Incorrect VS Code Settings

VS Code has a setting that controls the sidebar location. When set to “auto,” VS Code may fail to allocate a slot for the Copilot webview. Additionally, the window.titleBarStyle setting set to “custom” on Linux can interfere with webview rendering.

Steps to Open the Copilot Sidebar

Follow these methods in order. Test the sidebar after each method before moving to the next.

Method 1: Reload the VS Code Window

1. Open the command palette
   Press Ctrl+Shift+P on Windows or Linux, or Cmd+Shift+P on macOS.
2. Run the reload command
   Type Developer: Reload Window and press Enter. VS Code reloads the extension host and all UI panels. The Copilot sidebar should appear after the reload.

Method 2: Check and Change the Sidebar Location Setting

1. Open VS Code settings
   Press Ctrl+, (comma) on Windows and Linux, or Cmd+, on macOS.
2. Search for the sidebar location setting
   In the settings search bar, type sidebar.location.
3. Set the value to “left” or “right”
   Click the dropdown and select “left” or “right.” Do not select “auto.” The Copilot sidebar requires an explicit side assignment.
4. Reload the window
   Press Ctrl+Shift+P, run Developer: Reload Window, and check the Copilot icon in the activity bar.

Method 3: Disable Conflicting Extensions

1. Open the Extensions view
   Click the Extensions icon in the activity bar or press Ctrl+Shift+X.
2. Disable all extensions except Copilot
   Click the gear icon next to each extension and select “Disable.” Leave only GitHub Copilot and GitHub Copilot Chat enabled.
3. Reload the window
   Run Developer: Reload Window from the command palette.
4. Test the Copilot sidebar
   Click the Copilot icon. If the sidebar opens, one of the disabled extensions was the cause. Re-enable extensions one by one, reloading each time, until the sidebar stops working again. The last re-enabled extension is the conflict.

Method 4: Delete the Copilot Extension Cache

1. Close VS Code completely
   Exit all VS Code windows. Check the system tray to ensure no VS Code process remains running.
2. Open the VS Code extension cache folder
   On Windows, navigate to %USERPROFILE%\.vscode\extensions\github.copilot-\. On macOS and Linux, navigate to ~/.vscode/extensions/github.copilot-/. The exact folder name includes the version number, such as github.copilot-1.200.0.
3. Delete the cache subfolder
   Inside the Copilot extension folder, delete the folder named cache or .cache. Do not delete the entire extension folder.
4. Restart VS Code
   Open VS Code. The extension recreates its cache on startup. Click the Copilot icon to verify the sidebar opens.

If Copilot Still Has Issues After the Main Fix

Copilot Icon Is Missing from the Activity Bar

If the Copilot icon does not appear at all, the extension may not be installed correctly. Open the Extensions view, search for “GitHub Copilot,” and verify the extension shows as enabled. If it shows as disabled, enable it and reload. If it shows as installed but grayed out, reinstall the extension by clicking the gear icon and selecting “Install Another Version,” then picking the latest stable release.

Copilot Sidebar Opens But Shows a Blank White Panel

A blank white panel indicates a webview rendering failure. This usually happens when VS Code cannot load the extension’s HTML or JavaScript resources. The fix is to clear the VS Code webview cache. Press Ctrl+Shift+P, run Developer: Clear Editor Cache, then reload the window. If the problem persists, check your proxy settings. Go to File > Preferences > Settings, search for http.proxy, and ensure the proxy URL is correct. An incorrect proxy blocks the webview from fetching remote resources.

Copilot Sidebar Closes Immediately After Opening

This behavior is often caused by a keybinding conflict. The default keyboard shortcut for toggling the Copilot panel is Ctrl+Shift+I on Windows and Linux, or Cmd+Shift+I on macOS. If another extension or a user-defined keybinding uses the same shortcut, VS Code may close the panel right after opening it. Open the command palette, run Preferences: Open Keyboard Shortcuts, search for Copilot, and inspect the keybindings. Remove or change any conflicting bindings.

Item	Copilot Sidebar Not Opening	Copilot Sidebar Blank
Primary cause	Extension conflict, cache corruption, or sidebar location set to “auto”	Webview rendering failure due to cached HTML or proxy misconfiguration
Quick fix	Reload window or change sidebar location to “left” or “right”	Clear editor cache via command palette
Requires extension reinstall?	No, unless the extension is disabled or missing	No, unless clearing cache and proxy check fail
Affected by proxy settings?	No	Yes

After applying the correct fix, the Copilot sidebar should open reliably. If the sidebar still fails, check the VS Code logs for extension-specific errors. Open the command palette and run Developer: Toggle Developer Tools. In the Console tab, look for red error messages containing “copilot” or “webview.” Search the error text on the GitHub Copilot community forum to find a targeted solution. As a final step, reset VS Code to its default settings by running Developer: Reset Window State from the command palette. This clears all workspace-specific customizations without removing extensions.