Prismix
Developer 5 min read

GitHub Copilot Not Working

Copilot stopped suggesting code? Here’s how to tell if it’s a service outage or a local issue — and how to fix either.

GitHub Copilot live status

GitHub Copilot — live status

If Operational, the issue is local to your editor. Updated every 5 min. View incidents →

Step 1: Is it an outage or a local issue?

Before changing any settings, confirm whether the problem is GitHub’s servers or your local setup:

  1. Check prismix.dev/service/github-copilot for live status
  2. Check githubstatus.com for GitHub’s own status page
  3. Try a different file type (e.g., if Python fails, try a JavaScript file)

If Copilot shows Operational and other developers aren’t reporting problems, the issue is local.

VS Code: check the Copilot status icon

The bottom status bar in VS Code shows the Copilot state at all times:

  • Copilot icon (normal) — working correctly
  • Copilot icon + spinner — connecting to GitHub servers
  • Copilot icon + yellow warning — degraded service or quota warning
  • Copilot icon + X — disabled or auth error (click for details)

Click the icon to open the status menu with the specific error message.

7 fixes when Copilot stops working

1. Sign out and sign back in

The most common fix. Refreshes your auth token from GitHub’s servers.

# VS Code
Ctrl+Shift+P (Win/Linux) or Cmd+Shift+P (Mac)
→ "GitHub Copilot: Sign Out"
→ Sign back in with your GitHub account

2. Check your subscription status

Go to github.com/settings/copilot and verify your plan shows Active. Common issues:

  • Billing payment failed — update card and reactivate
  • Free trial expired — needs a paid plan
  • Team plan — check your org admin assigned your seat under Organization → Copilot → Seats

3. Enable Copilot for the file type

Copilot can be disabled per language. In VS Code, check Settings → GitHub Copilot → Enable and verify your file’s language is not in the exclusion list.

// settings.json — check this key:
"github.copilot.enable": {
  "*": true,
  "plaintext": false,  // ← language exclusions
  "markdown": false
}

4. Disable and re-enable the extension

In VS Code Extensions panel: right-click GitHub Copilot → Disable, then re-enable. This forces a fresh connection.

5. Check for conflicting extensions

Extensions like Tabnine or Codeium can conflict with Copilot. Disable them temporarily and test if Copilot suggestions return.

6. Check your network / proxy

Copilot requires outbound HTTPS to copilot-proxy.githubusercontent.com. If you’re on a corporate network with SSL inspection or firewall, your IT team may need to allowlist this domain.

7. Reinstall the extension

Uninstall GitHub Copilot (and GitHub Copilot Chat if installed), restart VS Code, then reinstall from the marketplace. This clears stale cached state.

JetBrains IDEs (IntelliJ, PyCharm, WebStorm)

  • Check the Copilot icon in the bottom-right status bar — click for the status menu
  • Sign out: File → Settings → GitHub Copilot → Log Out
  • Firewall: Allow api.github.com and copilot-proxy.githubusercontent.com
  • Plugin update: Plugins panel → check if GitHub Copilot has a pending update
🔔

Get notified the moment Copilot comes back

Star GitHub Copilot on Prismix to get a free email alert the moment service recovers from any outage. Also monitors 75+ other AI services.

Live status Set up alerts →
GitHub Copilot live status → Copilot status guide → Is Cursor down? → All guides →