VS Code SetupBeginner

How to Fix AI Suggestions Not Appearing in VS Code

Diagnose and fix common reasons Copilot, Continue, or Cline stop producing suggestions in VS Code.

8 minBeginner

When an AI assistant goes quiet, the cause is usually one of a handful of easy-to-check things: a sign-in that expired, a setting toggled off, a network block, or a quota you have hit. This guide is a checklist that works for Copilot, Continue, and Cline so you can find the problem quickly instead of reinstalling everything.

What you need

  • VS Code with at least one AI extension installed
  • Access to the account or API key the extension uses
  • About 6 minutes

Step 1: Check the status bar and sign-in

Look at the bottom status bar. A Copilot icon with a slash means it is disabled or signed out. Click it, and if it asks you to sign in, do so. For Continue and Cline, open their panel and confirm a model is selected and a key is present, because expired keys silently stop responses.

VS Code - status bar
main* UTF-8 LF JavaScript (Copilot: signed out)
----------------------------------------
Click the Copilot icon to sign in again
A struck-through icon signals a problem.

Step 2: Confirm the feature is enabled for this file

Suggestions can be disabled for a specific language. Open your settings and check the enable map. If the current file type is set to false, that is why nothing appears. Set it to true and the suggestions return.

settings.json
{
  "editor.inlineSuggest.enabled": true,
  "github.copilot.enable": {
    "*": true,
    "yaml": true
  }
}
The master toggle
If editor.inlineSuggest.enabled is false, no extension can show inline ghost text, no matter how it is configured. Check this setting first when completions vanish across every language at once.

Step 3: Check the network and the output log

These tools call a server, so a proxy, VPN, or firewall can block them. Open the Output panel, pick the extension's channel from the dropdown, and read the recent lines. Authentication and connection errors show up here in plain language.

VS Code - Output panel
OUTPUT [ GitHub Copilot v ]
----------------------------------------
[info] checking auth status
[error] request failed: 401 Unauthorized
[info] token expired, please sign in
The extension log often names the exact failure.

Step 4: Check quota, then reload

On a free or metered plan you can run out of completions or hit an API spend limit. Check your plan usage in the provider console. If everything looks correct but it still fails, run Developer: Reload Window from the Command Palette, which restarts the extensions cleanly.

Command Palette - reload
$>Developer: Reload Window
Reloading window...
Often clears stale extension state without losing your work
$
Work top down
Go through these steps in order. Most outages are sign-in or a disabled toggle, which take seconds to fix, so checking them before you touch the network or reinstall saves a lot of time.

Result

By checking sign-in, per-language settings, the inline suggest toggle, the output log, and your quota, you can find why an assistant stopped responding and fix it without a reinstall. In most cases the suggestions come back as soon as you re-sign in or re-enable the right setting.

Watch related tutorials

Tags
#troubleshooting#copilot#continue#cline#fix