Gathering Logs
If you’re having issues, the first step in the troubleshooting process is to retrieve the logs from your IDE. Here’s how you can get Codeium logs for each of the major IDEs:
Windsurf
-
Open the Command Palette (
Ctrl/Cmd + Shift + P
or go to View > Command Palette) -
Type in “Open Windsurf Logs” and select the option that reads “Open Windsurf Logs File”
-
Export or copy the logs and attach the file to your ticket.
Alternatively, you can also click on the three dots in the top right corner of the Cascade panel and select “Download Diagnostics”.
VS Code
-
Go to the Command Palette (
Ctrl/Cmd + Shift + P
or go to View > Command Palette) -
Type in “Show logs” and select the option that reads “Developer: Show Logs”
-
From the dropdown, select “Extension Host”
-
You should see something similar to the image below:
-
Change the dropdown in the top right that reads “Extension Host” and select “Codeium”
-
Export or copy the logs
JetBrains IDEs
Starting in extension version 1.10.0, the Chat Panel has an Extension Diagnostics button on the Settings page. This button will automatically collect relevant logs and parameters into a text file that can be downloaded.
-
Logs are written to the idea.log file. To locate this file, go to the Help > Show Log in Finder/Explorer menu option
-
Export or copy the logs
Eclipse
In Eclipse, logs are written to the following paths:
- Mac/Linux: ~/.codeium/codeium.log
- Windows: C:\Users<username>.codeium\codeium.log
Visual Studio
Go to view > output, select “Codeium” in the dropdown, and copy the logs.
NeoVim
Set g:codeium_log_file
to a path to a file in their vimrc and then relaunch vim.
Then the logs should be written to that file.