Don't stop here
Hand-picked guides our readers explore right after this one.
AI pair programming prompts for GitHub Copilot code completion and Chat
Read the guideMaster ChatGPT with advanced prompting techniques, mega-prompts, and proven frameworks
Read the guideWrite compelling college application essays with AI
Read the guideGitHub Copilot failures fall into five buckets: authentication (your GitHub token expired — usually a 401/403), network/proxy (requests to GitHub blocked), extension or IDE issues (the plugin itself), license or org policy (your plan or admin settings block Copilot), and — new in 2026 — credit/quota (a 402 'quota_exceeded' once your monthly GitHub AI Credits run out). Start at githubstatus.com, which now has two relevant components: 'Copilot' and the newer 'Copilot AI Model Providers' (covers upstream model outages). Copilot is also multi-model now — a picker across OpenAI (GPT-5.x), Anthropic (Claude Sonnet 4.6 / Opus 4.8), and an 'Auto' mode — so a single model being down doesn't mean Copilot is down. Most issues are fixable in under 10 minutes without reinstalling anything.
Copilot down and need to keep shipping?
If Copilot has stalled and you're trying to build something, Lovable is a separate AI app builder that turns a prompt into a working, deployed full-stack app — a fast way to keep making progress while Copilot is out. Free to start.
Affiliate link, we may earn a commission at no extra cost to you.
GitHub Copilot icon in the VS Code status bar shows a strikethrough, warning icon, or is grayed out
No inline code suggestions appear while typing, even after a long pause
VS Code output panel shows: 'GitHub Copilot could not connect to server. Extension activation failed'
Error: 'GitHub Copilot is not enabled for this account'
Error: 'Request failed: 401 Unauthorized' or '403 Forbidden' in Copilot logs
Error: '402 ... "code":"quota_exceeded"' or 'You have no quota' — monthly AI Credits exhausted
'You have exceeded your premium request allowance. We have automatically switched you to GPT-4.1'
Premium models greyed out, or an infinite loading spinner with no visible error
Copilot Chat panel loads but shows 'Authentication required' or stays blank
Suggestions were working but suddenly stopped after a VS Code or extension update
Copilot status shows 'Disabled by organization policy' in the status bar tooltip
GitHub Copilot authenticates via OAuth tokens stored locally. These tokens can expire or become invalid after password changes, 2FA reconfiguration, or GitHub account security events. The extension often fails silently rather than prompting you to re-authenticate, you just stop getting suggestions.
GitHub releases Copilot extension updates frequently. After GitHub makes backend changes, older extension versions stop communicating properly. VS Code's auto-update can lag 24-48 hours. Running an extension version more than 2-3 weeks old is a common cause of sudden failures.
GitHub Copilot requires access to api.github.com and copilot-proxy.githubusercontent.com. Corporate networks that block GitHub domains or require authenticated proxies will prevent Copilot from connecting. The error manifests as timeouts or connection failures, not authentication errors.
Copilot Individual requires a paid subscription ($10/month or $100/year) or an active free trial. Copilot for Business/Enterprise requires an organization administrator to assign you a seat. If your trial ended, billing failed, or your organization removed your seat, Copilot stops working immediately.
GitHub organizations can disable Copilot for members via policy settings. If your company's GitHub organization has Copilot blocked, you'll see 'Disabled by organization policy' even if you have a personal subscription. This requires admin action, individual users cannot override organization policies.
Some VS Code extensions that modify editor behavior (language servers, code formatters, other AI completion tools like Tabnine or Codeium) can conflict with Copilot's inline suggestion system. Additionally, certain VS Code settings like editor.inlineSuggest.enabled: false or editor.quickSuggestions set to false will suppress Copilot's suggestions.
When to try: First, rules out service-side issues immediately
Visit githubstatus.com and check TWO components: 'Copilot' (the service itself) and 'Copilot AI Model Providers' (upstream model outages — new in 2026). If the model-providers component is degraded, switching to a different model in the picker (or 'Auto') often gets you working again. Also check X/Twitter for 'GitHub Copilot down'; user reports often surface before the status page updates. If there's an active incident, wait for GitHub to resolve it.
When to try: Second, fixes most authentication-related failures
In VS Code: open the Command Palette (Ctrl+Shift+P / Cmd+Shift+P), type 'GitHub Copilot: Sign Out', press Enter. Wait for confirmation, then type 'GitHub Copilot: Sign In' and follow the OAuth flow in your browser. This refreshes your authentication token and resolves most '401 Unauthorized' and silent authentication failures. In JetBrains: Settings → Tools → GitHub Copilot → Sign Out, then Sign In.
When to try: If authentication refresh didn't fix it
In VS Code: go to Extensions sidebar (Ctrl+Shift+X), search for 'GitHub Copilot', and check for an Update button. Install it and restart VS Code. Also update 'GitHub Copilot Chat' if installed. To check your current version: click the gear icon on the Copilot extension → check version number. GitHub recommends keeping Copilot within the last 2 major releases for compatibility. In JetBrains: Settings → Plugins → GitHub Copilot → Update.
When to try: When you see 'not enabled for this account' or 401/403 errors
Go to github.com → click your profile photo → Settings → Billing and plans → Copilot. Check that your subscription shows 'Active'. If it's expired or shows payment issues, update your payment method and reactivate. For Copilot Business/Enterprise users: ask your GitHub organization admin to verify you have a seat assigned. You can also check your subscription status directly at github.com/settings/copilot.
When to try: When Copilot extension shows as healthy but no suggestions appear
Open VS Code Settings (Ctrl+, / Cmd+,) and search for 'inlineSuggest'. Make sure 'Editor: Inline Suggest: Enabled' is checked. Also search for 'quickSuggestions' and verify it's not set to false. Check that Copilot isn't disabled for the specific language you're coding in: open Command Palette → 'GitHub Copilot: Enable Completions' and confirm it's enabled. Check by opening VS Code Output panel (Ctrl+Shift+U), select 'GitHub Copilot' from the dropdown to see live logs.
When to try: For corporate network or proxy-related connection failures
If on a corporate network: open VS Code Settings → search for 'http.proxy' → enter your proxy URL (e.g., http://proxy.company.com:8080). If your proxy requires authentication, use http://user:[email protected]:8080. Also check 'http.proxyStrictSSL', set it to false if your corporate network uses SSL inspection. Alternatively, try with VPN disabled or ask IT to whitelist api.github.com and *.githubusercontent.com.
When to try: When Copilot was working, then stopped after installing a new extension
Disable other AI code completion extensions temporarily: Tabnine, Codeium, Amazon CodeWhisperer, and similar tools can conflict with Copilot's suggestion pipeline. In VS Code Extensions sidebar, disable them one by one and test Copilot after each. Also try disabling language-server heavy extensions if you're on a large project. Reload VS Code window (Ctrl+Shift+P → 'Developer: Reload Window') after each change.
When to try: When other fixes haven't worked and you want to diagnose the specific error
In VS Code: open the Output panel (View → Output, or Ctrl+Shift+U), select 'GitHub Copilot' from the dropdown. Look for the most recent error messages. Common messages and meanings: 'Extension activation failed' = authentication or network issue, 'Request failed: 401' = expired token (fix: sign out/in), 'Request failed: 403' = organization policy blocking or subscription issue, 'ECONNREFUSED' or 'ETIMEDOUT' = network/proxy blocking. The specific error message narrows the fix significantly.
Keep the GitHub Copilot VS Code extension updated, check for updates weekly if you use Copilot heavily
Bookmark githubstatus.com, Copilot has its own status component separate from GitHub's main service
If on a corporate network, set up proxy settings when you first configure Copilot, not after issues arise
Re-authenticate Copilot proactively after changing your GitHub password or reconfiguring 2FA
Avoid running multiple AI code completion tools simultaneously, pick Copilot or an alternative, not both
Contact GitHub support at support.github.com if: (1) Your subscription is active and billing current but Copilot still shows 'not enabled' after sign out/in, (2) You believe organization policy is incorrectly applied to your account, (3) Copilot logs show persistent 403 errors with no policy or billing explanation, (4) You're on Copilot Business/Enterprise and issues affect your whole team. For VS Code-specific issues not tied to authentication, the VS Code GitHub Copilot extension GitHub repo (github.com/microsoft/vscode-copilot-release) has an issues tracker where the team actively responds.
VS Code updates occasionally introduce settings changes, extension API changes, or workspace trust changes that break Copilot's integration. Fix sequence: (1) Update the Copilot extension itself to match the new VS Code version, (2) Check that workspace trust is enabled for your project folder (VS Code may have reset it after updating), (3) Sign out and back into Copilot. If you need to roll back, you can install a specific extension version from the VS Code marketplace VSIX file.
The status bar icon at the bottom of VS Code is your primary indicator. A Copilot icon with no warning = active and connected. A strikethrough = disabled for current file or language. A loading spinner = connecting. A warning triangle = authentication or connectivity issue. Click the icon for a menu showing current status and options. You can also open a .py or .js file, type a function comment, and wait 2-3 seconds for an inline suggestion to appear as a gray ghost text.
Two common reasons: (1) Organization policy, your company's GitHub organization may have Copilot disabled or restricted. Check with your GitHub organization admin. (2) Workspace trust, VS Code's workspace trust system restricts some features in untrusted workspaces. Click the trust indicator in the bottom-left of VS Code and mark your workspace as trusted. Copilot suggestions can also be disabled per-language via VS Code settings, which may be set differently in your work VS Code profile.
Yes — there's a genuine free tier now (no card required): Copilot Free gives limited code completions and chat per month. Paid plans are Pro ($10/mo), Pro+ ($39/mo), and Max ($100/mo) for individuals, plus Business ($19/user/mo) and Enterprise ($39/user/mo); students and open-source maintainers can get Pro free (education.github.com). As of June 2026, billing moved to usage-based GitHub AI Credits: each plan includes a monthly credit allowance, and code completions + next-edit suggestions don't consume credits on paid plans (so basic autocomplete keeps working even after you've used up credits on premium models).
Copilot Chat is a separate extension (GitHub Copilot Chat) from the inline suggestions extension (GitHub Copilot). They can fail independently. If inline suggestions work but Chat doesn't: update the Copilot Chat extension specifically, sign out and back in for the Chat extension, and check that your subscription tier includes Copilot Chat (available on all paid plans as of 2026). Copilot Chat requires a more recent VS Code version than basic Copilot, update VS Code if you're on an older version.
Your GitHub organization administrator has blocked Copilot usage for organization members. This is a GitHub organization-level setting under Settings → Copilot → Policies. Individual users cannot override this policy. Options: (1) Ask your organization admin to enable Copilot (they may need to purchase Copilot Business seats), (2) Use Copilot in repositories outside your organization using a personal GitHub account, (3) Use alternative tools (Tabnine, Codeium, Amazon CodeWhisperer) that don't have this restriction. Note: using a personal Copilot subscription on organization repositories may still be blocked by policy.
The Copilot plugin for JetBrains (IntelliJ, PyCharm, WebStorm, etc.) is separate from the VS Code extension and has independent updates and authentication. Common JetBrains-specific issues: (1) Plugin version is outdated, go to Settings → Plugins → GitHub Copilot → Update, (2) Authentication is separate, you need to sign in via the JetBrains plugin even if VS Code is signed in, (3) Older JetBrains IDE versions (pre-2022) have compatibility issues, update your IDE. Also check that 'Enable Copilot completions' is checked in Settings → Tools → GitHub Copilot. Verified June 2026.
Copilot uses the content of your current file plus context from nearby open files as input. It does not index your entire repository in real time (that's a Copilot Enterprise feature). By default, Copilot sends the text in your current file and a few surrounding files to GitHub's API for completion. You can check Copilot's telemetry settings at github.com/settings/copilot, this controls whether your code snippets are used to improve Copilot's models. For sensitive codebases, Copilot Business/Enterprise includes provisions to opt out of training data collection.
A 402 with 'quota_exceeded' (or 'You have no quota' in the VS Code output panel) means you've used up your monthly GitHub AI Credits for premium models — it's a billing/quota state, not an outage or auth failure (that would be 401/403). Fixes: check your credit balance in GitHub billing settings, enable paid overage if you want to keep using premium models, or switch to an included model — code completions and next-edit suggestions don't consume credits on paid plans, so basic autocomplete should still work. Org admins: after the June 2026 billing migration, a 'ghost' budget entry set to $0 caused whole orgs to hit 402 despite having credits — clearing that budget in org policy fixes it.
The message 'You have exceeded your premium request allowance. We have automatically switched you to GPT-4.1' means you've run out of premium-model credits, so Copilot fell back to an included model to keep you working. It's expected behavior, not a bug. To get premium models back, top up credits / enable overage, or wait for your monthly allowance to reset. If you'd rather not be downgraded, you can pin an included model in the picker.
Check githubstatus.com and look at both the 'Copilot' and 'Copilot AI Model Providers' components — if the model-providers one is degraded, switch models or use 'Auto' and you'll likely keep working. If both are green but Copilot still fails for you, it's local: update the extension, sign out and back in (fixes 401/403), check your credit balance (402), check org policy/content-exclusion, or check your proxy/VPN. A genuine outage shows up across many users at once on the status page and X/Twitter.
Copilot may be disabled for a specific language in your VS Code settings, or support for that language may be limited. Check: open Command Palette → type 'GitHub Copilot: Enable Completions', the menu shows per-language enable/disable state. Copilot has strong support for Python, JavaScript, TypeScript, Go, Ruby, and C#. It has weaker (but functional) support for less common languages. For fully unsupported languages, you won't get suggestions regardless of configuration. Verified June 2026.