Cody troubleshooting guide
Here are common troubleshooting steps to run before filing Cody bugs on the issue tracker or asking in our Discord. (We're always happy to help, though!)
VS Code extension
Cody is not responding in chat
- Ensure you are on the latest version of the Cody VS Code extension. You can run the VS Code command
Extensions: Check for Extension Updatesto check.
- Check the VS Code error console for relevant error messages. To open it, run the VS Code command
Developer: Toggle Developer Toolsand then look in the
Consolefor relevant messages.
Errors trying to install Cody on MacOS
If you are getting:
Command 'Cody: Set Access Token' resulted in an error command 'cody.set-access-token' not found
- Close VS Code
- Open Keychain Access.app
- Search for
- Delete the
vscodesourcegraph.cody-aientry in the System keychain on the left.
- Try opening VS Code again
If you are logged into Sourcegraph.com, only public open source repositories on this list are indexed. Please join the Sourcegraph Discord and message the
#cody-embeddings channel to get an open source repository added to the public index.
If you’re connected to a Sourcegraph Enterprise instance, please ask your site admin to Configure Code Graph Context for your Sourcegraph instance and then Enable Cody for your account.
If you've completed the above and still seeing your codebase showing up as
NOT INDEXED, try updating the
Cody: Codebase (
cody.codebase) setting in VS Code to the repository name as listed on your Sourcegraph instance.
For more information, see Generate Index to Enable Codebase-Aware Answers.