GitHub Copilot Not Suggesting Code: Practical Fixes for VS Code, JetBrains, and Visual Studio
TL;DR Start with Copilot sign-in, subscription or organization access, and the editor extension state before changing project code. Most silent failures come from disabled inline suggestions, stale authentication, workspace overrides,…
- Start with Copilot sign-in, subscription or organization access, and the editor extension state before changing project code.
- Most silent failures come from disabled inline suggestions, stale authentication, workspace overrides, unsupported file context, or network policy.
- Use the editor output logs before reinstalling everything; they usually show whether Copilot is blocked, unauthorized, disabled, or unavailable.
Overview
When GitHub Copilot is not suggesting code, the problem is usually somewhere in the editor integration path rather than in your project code. A useful first pass is to confirm that the right GitHub account is signed in, verify that the account has Copilot access, make sure inline suggestions are enabled, restart the editor integration, and test in a small supported source file. GitHub’s own Copilot docs describe the product and supported editor integrations at GitHub Copilot documentation, but day-to-day troubleshooting usually comes down to finding where the signal breaks: account, editor, workspace, language server, proxy, or organization policy.
- Sign out of GitHub in the editor, sign back in, and confirm the same account has Copilot access.
- Enable inline suggestions in the editor settings; Copilot can be installed but visually silent.
- Restart the extension host or IDE, then test in a new JavaScript, Python, or TypeScript file.
- Check user, workspace, and language-specific settings for overrides that disable Copilot or inline suggestions.
- Review Copilot output logs before reinstalling; logs separate auth, network, policy, and extension failures.
Symptoms
The common symptom is simple: you type code and no gray inline completion appears. In VS Code, the Copilot icon may still be visible, which makes the failure look inconsistent. In JetBrains IDEs or Visual Studio, the plugin can be installed while suggestions remain absent in one project. Some users also see Copilot Chat working while inline code completion does not, or the reverse. That distinction matters because chat, inline completion, authentication, and editor settings can fail independently. Avoid deleting settings immediately. First identify whether the issue affects every file, one workspace, one language, or only one editor.
Why This Happens
Copilot suggestions depend on several layers working at the same time: GitHub authentication, Copilot entitlement, editor extension activation, language context, network access, and local editor settings. A failure in any layer can make Copilot look idle. Organization policy can also matter when a work account manages Copilot access, but do not assume a policy change unless the account or admin page confirms it. Official troubleshooting guidance is available in GitHub’s Copilot troubleshooting documentation. The practical rule: check identity and extension state before changing workspace files or blaming the model.
Check Status, Account, and Basic Access
Verify the signed-in GitHub account
Confirm the editor is authenticated with the same GitHub account that has Copilot access.
Start with identity. In VS Code, use the Accounts icon in the Activity Bar, then check the signed-in GitHub account. You can also open the Command Palette with Ctrl+Shift+P on Windows/Linux or Cmd+Shift+P on macOS and run GitHub Copilot: Sign Out, then sign in again when prompted. In JetBrains IDEs, check Settings/Preferences > Version Control > GitHub for the GitHub account and Settings/Preferences > Plugins for the GitHub Copilot plugin state. In Visual Studio, check File > Account Settings and confirm the expected GitHub account is signed in. If you use both personal and organization accounts, this is the highest-value check because the wrong account can make Copilot appear installed but inactive. Also check whether your organization manages Copilot access. Do not infer subscription, plan, or rollout state from the extension icon alone.
Try a Clean Editor Session
Restart the editor integration, not just the file tab
Reload the window, restart the IDE, or restart the extension host so Copilot reconnects cleanly.
A clean session fixes many silent Copilot failures because the extension host, authentication token, or language server can be stale. In VS Code, open the Command Palette with Ctrl+Shift+P or Cmd+Shift+P and run Developer: Reload Window. In JetBrains IDEs, restart the IDE after confirming the Copilot plugin is enabled. In Visual Studio, close the solution and restart Visual Studio. Then test in a new file with a common language such as JavaScript or Python. This removes project-specific noise and tells you whether Copilot is generally available.
VS Code Command Palette
> Developer: Reload Window Reopens the current VS Code window and restarts extension activation. > GitHub Copilot: Sign Out > GitHub Copilot: Sign In
Confirm Inline Suggestions Are Enabled
Check editor completion settings
Copilot can authenticate correctly while inline ghost text is disabled by editor configuration.
In VS Code, Copilot depends on the editor’s inline suggestion UI. Open File > Preferences > Settings on Windows/Linux or Code > Settings > Settings on macOS, then search for Inline Suggest and confirm Editor: Inline Suggest Enabled is on. In settings JSON, the relevant setting is editor.inlineSuggest.enabled. Also check .vscode/settings.json in the workspace, because a repository can override your global preference. Language-specific blocks such as [python] or [javascript] can also change behavior for only one language. This is a common gotcha: Copilot Chat can still answer questions while inline completion remains hidden because the ghost-text UI path is disabled.
{
"editor.inlineSuggest.enabled": true,
"github.copilot.enable": {
"*": true
}
}
Test a Minimal Supported File
A large repository can hide the real cause. Create a temporary file outside the failing project and type a small function stub. Use a common language and avoid empty comments that provide no intent. Copilot is more likely to suggest when it has a clear local pattern, nearby symbols, or a specific function name. If suggestions appear in the temporary file, the problem is probably workspace settings, repository policy, file type detection, or conflicting extensions. If suggestions still do not appear, continue with authentication, logs, and network checks.
Disable Conflicting Completion Extensions
Reduce autocomplete competition
Other AI assistants, snippet engines, and aggressive language extensions can intercept or visually crowd completions.
If you run multiple AI coding tools, test Copilot alone. In VS Code, open Extensions, disable other autocomplete or AI completion extensions for the workspace, reload the window, and try the minimal file again. This matters most in VS Code because several extensions can contribute inline completions, code actions, and ghost text. The goal is not to remove competitors permanently; it is to isolate which provider owns the completion UI. My recommendation: use one inline AI completion tool per editor profile. Keep other tools for chat or code review if needed, but avoid stacking several ghost-text providers in the same workspace.
Read Copilot Output Logs
Logs are the dividing line between guessing and troubleshooting. In VS Code, open View > Output, then use the channel dropdown to select a GitHub Copilot-related channel if available. You can also use Developer: Show Logs… from the Command Palette and choose a relevant extension log when present. In JetBrains IDEs, use Help > Show Log in Explorer on Windows/Linux or Help > Show Log in Finder on macOS, and inspect plugin-related messages without sharing secrets. In Visual Studio, open View > Output and check available GitHub Copilot or extension-related output channels; command names and channel labels can vary by version. You are looking for categories, not necessarily exact strings: authentication failure, network failure, extension activation failure, disabled language, or unavailable service. Do not paste tokens or private repository paths into public forums. Redact account names, access tokens, hostnames, and proprietary file names before sharing diagnostics.
Useful log categories to look for:
- Authentication or authorization failure
- Network, proxy, TLS, or certificate failure
- Extension activation failure
- Language disabled or file type unsupported
- Organization policy or access restriction
Check Network, Proxy, VPN, and Certificates
Corporate networks can block Copilot while leaving GitHub.com reachable in a browser. The editor extension may call different endpoints than the website, and TLS inspection can break extension traffic. Test from another trusted network if policy allows, or disconnect a VPN briefly when permitted by your organization. If the issue only happens on a managed laptop, ask IT whether developer tools must use a configured proxy or custom certificate store. Do not bypass corporate security controls. The correct fix is usually proxy configuration or allowlisting through approved channels, not disabling protection.
VS Code-Specific Checks
For VS Code, confirm the GitHub Copilot extension is enabled globally and in the current workspace from the Extensions view. Then reload the window and inspect user, workspace, and remote settings. If you use Dev Containers, WSL, SSH, or Codespaces, remember that extensions can run locally or remotely depending on the environment. Microsoft documents Copilot behavior for VS Code in VS Code’s Copilot overview. The lesser-known gotcha is remote context: Copilot may be installed on the desktop side while your active development window expects it in the remote extension host. In a remote VS Code window, check the Extensions view sections for the local and remote sides, and install or enable Copilot where the workspace is actually running.
JetBrains and Visual Studio Checks
In JetBrains IDEs, verify that the GitHub Copilot plugin is installed, enabled, and authenticated inside that IDE instance. Use Settings/Preferences > Plugins to check plugin state, and use the IDE’s GitHub account settings under Settings/Preferences > Version Control > GitHub to confirm identity. Different JetBrains products can have separate plugin state, so IntelliJ IDEA working does not prove PyCharm or WebStorm is configured the same way. Restart after plugin changes. In Visual Studio, confirm the GitHub account under File > Account Settings, then check that Copilot is available for the current Visual Studio installation and workload. If one IDE works and another does not, the GitHub account is less likely to be the root cause. Focus on plugin state, IDE updates, proxy configuration, and per-IDE settings. Do not assume all editors share the same Copilot session.
Browser and GitHub Web Checks
Browser checks are useful when the problem involves GitHub.com, Copilot settings pages, or account confirmation. Try a clean browser profile, disable privacy extensions temporarily, and sign in again. Browser troubleshooting does not directly fix inline completions inside an IDE, but it can confirm that the account can access GitHub normally and that organization settings are visible. If a browser shows account or organization access issues, fix those before changing IDE settings. If the browser is fine and only one editor is silent, return to extension logs.
When Not to Reinstall Copilot
Reinstalling the extension is overused. Avoid it when logs clearly show account authorization, proxy, or organization policy problems; reinstalling will not change those. Also avoid reinstalling before checking workspace settings, because a repository-level setting can disable suggestions again immediately after reinstall. Reinstall only after you have confirmed the account is correct, inline suggestions are enabled, a minimal file fails, conflicting extensions are disabled, and logs point to extension activation or corruption. This order preserves evidence and avoids turning a small settings issue into a profile repair job.
Fix the narrowest failing layer first: account, editor UI, extension host, workspace, network, then reinstall.
If It Still Fails
If GitHub Copilot still does not suggest code, capture the exact environment and failure pattern before escalation. Note the editor name, operating system, whether Copilot Chat works, whether inline completion fails in every file, and whether another network changes the behavior. Include redacted log categories, not secrets. Then use GitHub’s official support or community route from the Copilot documentation. If this is a managed organization account, contact the GitHub organization owner or internal IT team first, because access and policy settings may not be visible to you.
FAQ
Why is GitHub Copilot installed but not suggesting code?
Copilot can be installed while suggestions are disabled by account state, editor settings, workspace configuration, extension activation, or network policy. Start by confirming the signed-in GitHub account and enabling inline suggestions.
Why does Copilot Chat work but inline suggestions do not?
Chat and inline completion use different editor surfaces. Chat can work while ghost-text suggestions are hidden by inline suggestion settings, language settings, workspace configuration, or a conflicting completion extension.
Should I reinstall the GitHub Copilot extension?
Reinstall only after simpler checks fail. Verify sign-in, access, inline suggestions, minimal-file behavior, conflicting extensions, and output logs first. Reinstalling does not fix organization policy or proxy blocks.
Can a workspace disable Copilot suggestions?
Yes. Workspace or language-specific editor settings can override global preferences. Check repository settings files and editor configuration before assuming Copilot itself is unavailable.
Why does Copilot work in one editor but not another?
Each editor has its own plugin, authentication flow, settings, and extension host. If Copilot works in VS Code but not JetBrains or Visual Studio, focus on that IDE’s plugin state and logs.
Can VPN or corporate proxy settings stop Copilot suggestions?
Yes. A browser may reach GitHub while the editor extension fails through proxy, TLS, or certificate inspection. Use approved network configuration and avoid bypassing company security controls.
What should I send to support?
Send the editor name, operating system, account type, whether Chat works, whether a minimal file fails, and redacted log categories. Do not send access tokens, private repository contents, or internal hostnames.