DEV Community

Marcus Rowe
Marcus Rowe

Posted on • Originally published at techsifted.com

GitHub Copilot Chat Not Working in VS Code: 10 Fixes for 2026

#githubcopilot #copilotchat #vscode #aicoding

Copilot Chat and general Copilot autocomplete break in different ways. If your inline suggestions are working fine but Chat is broken — you have a Chat-specific issue. These two features use different components, different auth flows, and different extension versions.

I've debugged this in my own VS Code setup more times than I'd like. Here's the breakdown.

First: Chat vs. Autocomplete

Quick triage. Open a code file and start typing. Does Copilot autocomplete work (ghost text suggestions appearing)?

  • Autocomplete works, Chat broken: You have a Chat-specific issue. Continue here.
  • Both broken: You have a broader Copilot problem — check your GitHub subscription status and main extension authentication first.
  • Only Chat pane blank but inline chat (Ctrl+I) works: Skip to Fix 3.

Fix 1: Update the Copilot Chat Extension

This solves more issues than anything else. The Copilot Chat extension updates frequently, and older versions have known bugs with VS Code 1.88+ API changes.

  1. Open Extensions panel (Ctrl+Shift+X)
  2. Search "GitHub Copilot Chat"
  3. Click the extension. If an update button is available, click it.
  4. Reload VS Code after updating

Do the same for the base "GitHub Copilot" extension while you're at it — they sometimes have dependency relationships.

Fix 2: Authentication Loop — Sign-In Keeps Repeating

What you see: Copilot Chat prompts you to sign in. You sign in via browser. You're redirected back to VS Code. Chat prompts you to sign in again. Repeat forever.

The token storage issue. VS Code stores OAuth tokens in your OS keychain (macOS Keychain, Windows Credential Manager, Linux Secret Service). If the keychain entry is corrupted or the keychain service is inaccessible, the token can't be saved and the auth loop continues.

Fixes:

  1. Sign out and back in from VS Code. Command Palette (Ctrl+Shift+P) > "Sign out of GitHub" > Sign back in.

  2. Clear the stored credential manually.

    • macOS: Open Keychain Access, search "github.com", delete GitHub-related entries
    • Windows: Open Credential Manager > Windows Credentials, delete GitHub entries
    • Linux: Use secret-tool clear service GitHub user <yourusername> or the GNOME Keyring tool

  3. Try a different browser for the OAuth flow. Sometimes the OAuth redirect fails to return properly in certain browser configurations. If you're using Firefox with strict privacy settings, try Chrome.

  4. Disable and re-enable the extension. Sometimes clears stale state without the full sign-out flow.

Fix 3: Chat Pane Blank or Shows Loading Forever

What you see: You open the Copilot Chat sidebar and it's blank — white or gray — or shows a loading spinner that never resolves.

Extension initialization failure. This usually means the Chat extension's webview failed to initialize. Common causes: extension conflicts, VS Code webview cache corruption, or the extension loaded before VS Code's authentication state was ready.

Fixes:

  1. Reload the VS Code window. Command Palette > "Developer: Reload Window". This is the fastest first step — it re-initializes all extensions.

  2. Clear the extension host. Command Palette > "Developer: Restart Extension Host". Less disruptive than a full window reload, sometimes sufficient.

  3. Check for conflicting extensions. Other AI coding extensions (Cursor, Tabnine, Codeium) can conflict with Copilot Chat's webview. Temporarily disable them and see if Chat loads.

  4. Try in a fresh VS Code profile. File > Preferences > Profiles > Create Profile. A fresh profile with only Copilot Chat installed will confirm if your main profile has a conflict.

Fix 4: Inline Chat Not Triggering (Ctrl+I)

What you see: You press Ctrl+I (or your inline chat keybind) in the editor and nothing happens. No chat input appears inline.

Workspace trust restriction. VS Code's workspace trust system can restrict extension functionality in untrusted folders. If you opened a project from an unknown source, VS Code may have marked it untrusted.

  • Check: The bottom left corner of VS Code shows a shield icon for untrusted workspaces
  • Fix: Click the shield, or Command Palette > "Manage Workspace Trust" > Trust the workspace

Language mode not set. Inline chat is context-sensitive to file type. In a file without a recognized language mode (shown in the bottom right of VS Code), inline chat activation can fail.

  • Fix: Click the language mode selector in the bottom right and set the appropriate language

Keybinding conflict. Another extension or OS shortcut may have captured Ctrl+I.

  • Fix: Command Palette > "Keyboard Shortcuts" > search "inline chat" and check if the binding is listed and not overridden

Fix 5: Chat Context Window Errors

What you see: A message like "Context too large" or Chat refusing to process a request because the context exceeds limits.

Copilot Chat has a context window limit. When you use /workspace or add many files with #file, the accumulated context can exceed this limit.

Fixes:

  • Remove explicit file references you don't need. Use #file:specificfile.ts instead of /workspace when you only need context from one or two files.
  • Start a new chat session. Context accumulates across a conversation — a fresh session starts empty.
  • For large codebases, ask Copilot to focus on specific functions or files rather than the whole project.

Fix 6: Chat Doesn't Know About My Codebase

What you see: Copilot Chat gives generic answers that don't account for your specific code. You ask "how does authentication work in this project" and get a generic answer.

Copilot Chat's workspace context requires explicit activation. It doesn't passively read your whole codebase.

Fixes:

  • Use @workspace in your prompt: "@workspace how does authentication work?" This tells Chat to actively index and reference your workspace.
  • Use #file to specify relevant files: "Explain how #file:auth/middleware.ts handles token validation"
  • Make sure the Copilot Chat extension has indexing permissions — first use of @workspace triggers an indexing process that may take a few minutes on large projects.

Fix 7: Chat Available But Missing Model Options

In 2026, Copilot Chat supports multiple model selections (GPT-4o, Claude, Gemini depending on your plan). If the model selector is absent or some models are missing:

  • GitHub Copilot Individual plan: Limited model options. GPT-4o is typically available; advanced models may require Copilot Business or Enterprise.
  • Enterprise SSO accounts: Organization admins can restrict which models are available. If you're on a corporate account, your IT admin may have restricted model selection.

Check your plan's model availability at github.com/features/copilot/plans.

Fix 8: Copilot Chat Not Working After VS Code Update

VS Code major version updates (especially 1.88+) changed internal APIs that Copilot Chat depended on. If Chat broke right after a VS Code update:

  1. Update the GitHub Copilot Chat extension to the latest version first
  2. If the extension hasn't updated yet (recently released VS Code version), check GitHub's Copilot extension repository for known issues
  3. Temporary workaround: VS Code allows installing older versions — if the latest VS Code version has a compatibility issue with the current Chat extension, you can roll back VS Code temporarily

Fix 9: Chat Slow to Respond

Copilot Chat's response speed depends on GitHub's backend infrastructure and which model is selected. GPT-4o responses in Chat are faster than some alternatives; Claude-based responses can be slower.

If Chat is dramatically slower than usual:

  • Check githubstatus.com for Copilot service incidents
  • Try switching to a different model in the Chat model selector
  • A slow network connection to GitHub's API can compound the issue

Fix 10: Chat Not Showing Suggested Follow-ups

Minor but worth mentioning. If Copilot Chat used to show suggested follow-up questions but stopped, this is usually a setting that got reset.

Check VS Code settings (Ctrl+,) and search "copilot chat follow up". The github.copilot.chat.followUps setting should be set to "always" or "firstOnly" rather than "never".

For general GitHub Copilot issues — autocomplete not working, billing, subscription — the GitHub Copilot not working guide covers the broader issues. Chat-specific problems are a distinct subset. If you're trying to decide whether Copilot's Chat feature justifies the subscription cost on its own, that's worth comparing against standalone tools like Cursor where Chat and code editing are more deeply integrated.

Top comments (0)