Sourcegraph Cody Not Working in VS Code

How to fix it

Try these in order — the most common fix is first.

1. 1. Update and read the logs

   Copy steps
   1. Run Extensions: Check for Extension Updates
   2. Run Developer: Toggle Developer Tools and look at the Console
   3. Open View > Output and select Cody by Sourcegraph; enable Cody > Debug: Verbose for more detail
   Did this fix it? Yes No

2. 2. Fix the macOS keychain error

   Copy steps
   1. Close VS Code
   2. Open Keychain Access and delete the vscodesourcegraph.cody-ai entry
   3. Reopen VS Code and sign in again (fixes 'Command cody.set-access-token not found')
   Did this fix it? Yes No

3. 3. Check your network

   Copy steps
   1. Disable VPNs, anonymizers and open proxies (a Cloudflare 403 Forbidden is the usual symptom)
   2. If slow, email support@sourcegraph.com with your location, proxy setup and models used
   Did this fix it? Yes No

Symptoms

Chat does not respond, completions are slow or missing, or the extension shows errors after install or update.

Why it happens

• Outdated extension
• Stale keychain entry (macOS)
• VPN, proxy or anonymizer blocking requests
• Account on a discontinued plan (Free or Pro)
• Files excluded by admin contextFilters

This guide also covers

• cody not working vscode
• sourcegraph cody extension not responding
• cody vs code slow
• cody set-access-token not found

Other Sourcegraph errors

• Sourcegraph Cody Free and Pro Discontinued: What Happened and What to Do
• Sourcegraph Cody Sign-In Error: Authentication Failed or Signed Out on Restart
• Sourcegraph Cody Not Working in JetBrains (IntelliJ, Android Studio)
• Sourcegraph Cody Rate Limit or Usage Limit Reached
• Sourcegraph Search Not Finding Results
• Sourcegraph Repository Not Cloning or Not Updating
• Sourcegraph Search Slow or Timing Out (Zoekt Crash Loop)
• Sourcegraph Upgrade Failed: Dirty Database Migration Error