GitHub Copilot Not Working: Fixes for VS Code, JetBrains, and CLI
GitHub Copilot stops working most often because of an expired or inactive subscription, a failed authentication token, a firewall blocking GitHub's AI endpoints, or a version mismatch between the Copilot extension and your editor. Start by checking your subscription at github.com/settings/copilot, then sign out and back into the extension. Most issues resolve with a token refresh or extension update.
Why GitHub Copilot Stops Working
Copilot is an extension that connects your editor to GitHub's AI backend. Issues can occur in the editor layer, the authentication layer, or the network layer.
- Subscription not active — Free trial ended, seat not assigned by organization, or payment issue
- Authentication expired — GitHub token needs to be refreshed by signing out and back in
- Network/firewall block — Corporate proxies and firewalls frequently block Copilot's endpoints
- Extension out of date — Old extension versions can stop working after GitHub updates the API
- Editor or OS conflict — Version incompatibilities between the extension and the IDE
Step-by-Step Fix
1. Check Your Copilot Subscription
Go to github.com/settings/copilot and confirm:
- Your subscription shows as Active
- If on an organization plan, confirm a seat has been assigned to your account
- If using a free trial, confirm it has not expired
This is the most common reason Copilot suddenly stops working. If your subscription is inactive, no other fix will restore suggestions.
2. Sign Out and Sign Back In (VS Code)
- Open the Command Palette: Ctrl+Shift+P (Cmd+Shift+P on Mac)
- Type GitHub Copilot: Sign Out and run it
- Wait for sign-out to complete
- Run GitHub Copilot: Sign In from the command palette
- Complete the browser-based GitHub authorization
- Return to VS Code and wait for Copilot to reconnect
This refreshes your authentication token, which is the fix for most persistent failures.
3. Update the Copilot Extension
Outdated extension versions lose compatibility when GitHub updates their API:
- Open the Extensions panel in VS Code (Ctrl+Shift+X)
- Search for GitHub Copilot
- Click Update if available
- Also update GitHub Copilot Chat if installed
- Reload VS Code after updating
4. Check the Copilot Status Bar Icon
In VS Code, look at the bottom status bar for the Copilot icon (looks like two overlapping circles or a GitHub mark). Click it to see detailed status and recent error messages. This often shows exactly what is wrong.
Common status messages and what they mean:
- "Copilot is disabled for this file type" → enable it in settings for this language
- "Not signed in" → sign in via command palette
- "Quota exceeded" → you have hit usage limits, wait or upgrade
5. Fix Network and Proxy Issues
If you are on a corporate network:
- VS Code settings → search for proxy
- Set HTTP Proxy to your corporate proxy address (ask your IT team)
- Set Proxy Strict SSL to false if your company uses certificate inspection
You can also try setting the proxy directly: "http.proxy": "http://yourproxy:port" in VS Code settings.
To test if the network is the issue, switch to a phone hotspot and check if Copilot works. If it does, your corporate network is the problem.
6. Disable Conflicting Extensions
Some extensions conflict with Copilot's suggestion system, especially other autocomplete tools. Disable competing autocomplete extensions and test:
- Tabnine
- Kite
- IntelliCode
- Any other AI completion extension
Only one AI completion extension should be active at a time.
7. Reinstall the Extension
If all else fails:
- Uninstall GitHub Copilot and GitHub Copilot Chat from Extensions
- Reload VS Code
- Reinstall both extensions from the VS Code Marketplace
- Sign in again
Common Mistakes to Avoid
- Not checking the subscription first — If your trial ended or your org admin did not assign you a seat, no amount of reinstalling will fix it.
- Running multiple AI autocomplete extensions simultaneously — They interfere with each other. Disable all but Copilot.
- Forgetting to update after a major VS Code release — Major VS Code updates sometimes require extension updates that lag by a few days.
- Not configuring VS Code's proxy settings on corporate networks — VS Code does not automatically use system proxy settings for extension traffic. Configure it explicitly.
Copilot Usage Limits
GitHub Copilot has usage limits depending on your plan:
- Free tier (if available): Limited completions and chat interactions per month
- Individual: Generally high limits with no hard daily cap for normal use
- Business/Enterprise: Controlled by organization policy, may have restrictions per repository or file type
If suggestions suddenly slow down or stop mid-session, you may have hit a rate limit. Wait a few minutes and try again. Unlike some AI tools, Copilot does not always show an explicit rate limit message — suggestions simply stop appearing.
Related Articles
Common Mistakes to Avoid
- Troubleshooting the wrong account or workspace.
- Retrying without checking whether there is an active outage or plan restriction.
- Clearing local state only after multiple failed attempts instead of testing in a clean browser first.
What to Gather Before Contacting Support
- Capture the exact error message and the time it happened.
- Record whether the issue happens on another browser, device, or network.
- Note which account, workspace, or subscription plan is affected.
Explore more GitHub Copilot errors & bugs fixes
See related guides in the same topic cluster to troubleshoot adjacent issues faster.
Browse all GitHub Copilot errors & bugs guides →Frequently Asked Questions
Related Issues
Continue with nearby fixes in the same topic cluster to rule out adjacent causes faster.
ChatGPT Network Error: Why It Happens and How to Fix It
A ChatGPT network error means the connection between your browser and OpenAI's servers was interrupted. The most common causes are unstable internet, VPN interference, browser extension conflicts, or OpenAI server issues. Fix it by refreshing, switching networks, disabling VPN, or trying incognito mode. If the error only appears on long responses, enable the regenerate option and break your prompt into shorter parts.
ChatGPT Something Went Wrong: 7 Fixes That Actually Work
The 'Something went wrong' error in ChatGPT is a generic catch-all that usually means a session problem, a corrupted browser cache, or a temporary server issue. Fix it by signing out and back in, clearing your cache, or trying a private browser window. If it appears on every conversation, your account session may be corrupted and needs a full reset.
Claude Something Went Wrong: Causes and Fixes
The 'something went wrong' error in Claude is a generic message that covers session issues, browser problems, and temporary server errors. Start by refreshing the page and signing out then back in. If the error persists, clear your browser cookies for claude.ai and try a private window. This error almost never indicates an account problem — it is usually a temporary connection or session issue.
Cursor Not Working: Fixes for the Most Common Errors
When Cursor stops working, the most common causes are a failed AI model connection, an expired API key or subscription, a corrupted extension state, or a VS Code compatibility issue. Start by checking your Cursor account status at cursor.com, then reload the window with Ctrl+Shift+P → Reload Window. Most Cursor issues are resolved by signing out and back in or reinstalling the app.
Gemini Not Working: 8 Fixes for the Most Common Errors in 2026
When Gemini stops working, start with the basics: check Google's status page, clear your browser cache, sign out and back in with your Google account, and try a different browser. Most Gemini outages and loading errors resolve within minutes using one of these steps. If Gemini Advanced features are missing, check that your Google One subscription is active.
Claude API Key Not Working? Fix Auth Errors, Org Mismatch, and Permissions
If API auth fails, verify key scope, org/project, and environment variables. Rotate the key if compromised and check rate limits.