GitHub Copilot not showing in VS Code: 6 causes in diagnostic order

GitHub Copilot can stop showing suggestions, hide its status bar icon, or appear to be installed but do nothing — all for different reasons. This page covers the six causes in the order you should check them, from the simplest (it's toggled off) to the more complex (proxy configuration and content exclusion rules).

What "not showing" looks like

GitHub Copilot shows as missing in several distinct ways — identifying which one you have narrows the cause immediately:

What was verified on 5 September 2026 — and what was not

This page cannot be reproduced in a headless test environment (Copilot needs a signed-in VS Code window), so instead every concrete claim below was checked against GitHub's current documentation and the Marketplace listing on this date. Three things changed as a result.

1. Read the log before guessing. GitHub's own troubleshooting order is: View → Output, then pick GitHub Copilot in the dropdown on the right. For more detail, Command Palette → Developer: Set Log Level → choose the GitHub Copilot Chat (or GitHub) extension → Trace, reproduce, then set it back to Info. The raw files are in Command Palette → Developer: Open Extension Logs Folder. For network problems specifically, Command Palette → Developer: Chat Diagnostics has a Reachability section that tells you which Copilot endpoint is unreachable — that single screen resolves Cause 4 faster than any proxy guesswork.

2. The endpoint list on this page was incomplete. GitHub's allowlist reference (checked 5 Sept 2026) lists, for the editor to work at all: https://github.com/login/*, https://api.github.com/user, https://api.github.com/copilot_internal/* (authentication and entitlement), https://copilot-proxy.githubusercontent.com and https://origin-tracker.githubusercontent.com (suggestions), https://*.githubcopilot.com/* — with plan-specific hosts *.individual.githubcopilot.com, *.business.githubcopilot.com, *.enterprise.githubcopilot.com — plus https://default.exp-tas.com (experimentation) and https://copilot-telemetry.githubusercontent.com/telemetry. Two quick reachability probes GitHub documents: https://copilot-proxy.githubusercontent.com/_ping and https://api.githubcopilot.com/_ping. A firewall that only opened the four hosts previously listed here can still leave Copilot silently dead on the entitlement check.

3. Certificate errors have specific names. If the Output log shows "certificate signature failure", "custom certificate" or "unable to verify the first certificate", GitHub attributes it to a corporate proxy that intercepts TLS with its own certificate. The documented VS Code workaround is the Proxy Strict SSL setting (http.proxyStrictSSL) — the same setting Cause 4 describes — with the caveat that it should be a last resort agreed with your IT team.

Corrected: earlier versions of this page stated a minimum VS Code version of 1.82. GitHub's docs and the Marketplace listing (GitHub Copilot 1.388.0 on 5 Sept 2026) do not publish a fixed floor, and the extension is updated far more often than VS Code, so the rule is simply: update VS Code when the Extensions panel says the current Copilot build is incompatible. The Marketplace listing confirms Copilot installs as two extensions — GitHub.copilot and the companion GitHub.copilot-chat — which is why Cause 6 exists.

Not verified on this date: the exact status-bar icon states, the current settings key for per-language enablement, and any behaviour that requires a live signed-in session. Those sections are unchanged and should be read as guidance.

Cause 1: Copilot disabled for the current file or language (most common)

Copilot can be enabled or disabled per language type and per file path. If someone — or an automated workspace config — set "github.copilot.enable" to false for the current language, suggestions silently stop. The status bar icon shows a slash to indicate this state.

Fix:

1. Click the Copilot icon in the VS Code status bar (bottom right).
2. If you see "Enable Completions" for the current language, click it.
3. To check all enabled languages: open Settings (Cmd+, / Ctrl+,), search for github.copilot.enable, and verify the language you're working in is set to true or is not explicitly set to false.
4. Also check .vscode/settings.json in your workspace root — a workspace-level setting overrides user settings.

Cause 2: Extension not activated or failed to load

If the Copilot icon is completely absent from the status bar, the extension didn't activate. Common reasons:

• VS Code too old for the current Copilot build: the Extensions panel will say the extension is incompatible with your VS Code version. Check Help → About and update. (GitHub does not publish a fixed minimum; earlier versions of this page claimed 1.82 — see the verification note above.)
• Extension error: open the Extensions panel (Ctrl+Shift+X), find GitHub Copilot, and look for a warning icon or error message.
• Conflicting extension: some extensions that modify IntelliSense behavior can prevent Copilot from activating.

Fix:

1. Run Developer: Show Running Extensions from the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) to check if GitHub Copilot is listed as active.
2. If it shows an error, click the extension, read the GitHub Copilot Output channel, and update VS Code if the error is an incompatibility.
3. Try disabling other AI/IntelliSense extensions temporarily to rule out a conflict.
4. As a last resort: uninstall and reinstall the GitHub Copilot extension.

Cause 3: Subscription lapsed or not assigned

Copilot shows the icon but produces no suggestions if your subscription has expired, wasn't renewed, or (in a team/enterprise account) your seat was removed by an admin. There's usually no on-screen error — suggestions just silently stop appearing.

Fix:

1. Go to github.com/settings/copilot.
2. Check whether Copilot is shown as active for your account. If not, you'll see an option to start a trial or subscribe.
3. For GitHub Copilot Business/Enterprise: ask your org admin to confirm your seat assignment at Settings → Copilot → Access.
4. After confirming subscription status, sign out of GitHub in VS Code and sign back in: Command Palette → GitHub: Sign Out, then GitHub: Sign In.

Cause 4: Proxy or firewall blocking Copilot's endpoints

GitHub Copilot requires HTTPS access to these endpoints (from GitHub's allowlist reference, checked 5 Sept 2026):

https://github.com/login/*                              authentication
https://api.github.com/user                              user / entitlement check
https://api.github.com/copilot_internal/*               user / entitlement check
https://copilot-proxy.githubusercontent.com            suggestions
https://origin-tracker.githubusercontent.com           suggestions (public-code detection)
https://*.githubcopilot.com/*                           suggestions API (all plans)
https://*.individual.githubcopilot.com                  Copilot Individual
https://*.business.githubcopilot.com                    Copilot Business
https://*.enterprise.githubcopilot.com                  Copilot Enterprise
https://default.exp-tas.com                             client experimentation
https://copilot-telemetry.githubusercontent.com/telemetry   telemetry

# quick probes GitHub documents:
https://copilot-proxy.githubusercontent.com/_ping
https://api.githubcopilot.com/_ping

If your network has a proxy, VS Code doesn't pick it up automatically — you must configure it explicitly. If TLS inspection is active on these domains, Copilot's certificate validation fails; the Output channel then shows "certificate signature failure", "custom certificate" or "unable to verify the first certificate" while the editor itself shows nothing.

Fix — configure proxy in VS Code:

1. Open Settings → search for http.proxy.
2. Set it to your proxy URL, e.g.: http://proxy.company.com:8080
3. If your proxy requires authentication: http://user:password@proxy.company.com:8080
4. Set http.proxyStrictSSL to false if your proxy does TLS inspection (only do this if your IT team confirms the proxy is trusted).

Alternatively, ask your network admin to add the Copilot domains to the TLS inspection bypass list.

Cause 5: Content exclusion rules

GitHub Copilot Business and Enterprise accounts support content exclusion — admins can block Copilot from activating on specific file paths, repositories, or file types. If an exclusion rule covers the files you're working in, Copilot will appear to be installed and active but produce no suggestions.

Fix:

1. Check the Copilot icon tooltip — hover over it to see if it says "Content excluded by your organization."
2. If so, contact your GitHub org admin. Exclusion rules are configured at the org level and individual users can't override them.
3. If you're an admin: go to your org's Settings → Copilot → Content exclusion to review and update the rules.

Cause 6: Copilot Chat panel missing (different extension)

The inline suggestions and the Copilot Chat panel are two separate extensions: GitHub Copilot and GitHub Copilot Chat. If only the Chat panel is missing, the Chat extension may not be installed.

Fix:

1. Open Extensions (Ctrl+Shift+X) and search for GitHub Copilot Chat.
2. Install it if it's missing.
3. If it's installed but the panel still doesn't appear: open the Command Palette and run GitHub Copilot Chat: Focus on Chat View.

FAQ

Copilot worked yesterday and stopped today with no changes on my end. What happened? The most common cause is a subscription billing issue (auto-renewal failed) or a GitHub service disruption. Check githubstatus.com first, then verify your subscription at github.com/settings/copilot.

Can I use GitHub Copilot offline? No — Copilot requires an active internet connection to the GitHub API for every completion request. There is no offline or local inference mode.

Copilot suggestions appear but are always wrong for my codebase. Is that a different issue? Yes — that's a context or model quality issue, not a "not showing" issue. Copilot Chat's workspace indexing (@workspace) can help it understand your codebase better.

Related

• Cursor authentication failed: 5 causes & fixes
• Cursor vs GitHub Copilot: which is better for your workflow?
• Claude Code permission denied: what it means & how to fix it

Verified on 5 September 2026 against GitHub's Copilot troubleshooting, log-viewing and allowlist documentation and the Marketplace listing (GitHub Copilot 1.388.0): endpoint list, log/diagnostic commands, certificate error strings and the two-extension structure. Live editor behaviour was not reproduced on this date; the previously stated VS Code 1.82 minimum was removed as unverifiable.