Codeium Not Working? Fix Common Issues

Completions not appearing

1. 1
   Check sign-in status: Run "Codeium: Sign In" from the Command Palette (Ctrl+Shift+P / Cmd+Shift+P). If you are not authenticated, completions will not appear.
2. 2
   Check inline suggestion setting: Codeium uses VS Code's inline suggestion slot. Ensure "Editor: Inline Suggest Enabled" is on in VS Code settings. Press Escape then type again if suggestions seem stuck.
3. 3
   Conflict with GitHub Copilot: Both Codeium and Copilot use the same inline suggestion slot. If Copilot is enabled, its suggestions may suppress Codeium. Disable Copilot temporarily with "GitHub Copilot: Disable Completions" from the Command Palette to test.
4. 4
   Check Output → Codeium log: View → Output → select "Codeium" from the dropdown. Error messages here indicate what is wrong with the language server.
5. 5
   Restart the language server: Run "Codeium: Restart Language Server" from the Command Palette. This restarts the local server without reinstalling the extension.

Sign-in / authentication issues

Codeium supports two sign-in methods: browser OAuth (default) and API token (fallback for environments where OAuth callback fails).

If the browser OAuth loop does not complete: clear cookies for codeium.com in your browser, or switch to the token method. To use a token:

1. Go to codeium.com/account/settings and click Get API Key.
2. Copy the token shown.
3. Run "Codeium: Provide Authentication Token" from the VS Code Command Palette and paste the token.

For corporate environments: Codeium Enterprise uses a self-hosted server at a custom URL. If your org uses Enterprise, the extension must be configured with the internal server URL in settings — contact your admin for the endpoint.

Language server crash / high CPU

Check Output → Codeium for the crash reason. Common causes and fixes:

• Node.js version: Codeium requires Node.js 16 or later. Run node --version to check. Update Node via nvm or the official installer.
• Antivirus blocking the binary: Add the Codeium language server binary to your antivirus exclusion list. The binary lives inside the extension folder under ~/.vscode/extensions/codeium.*.
• Clear the cache: Delete ~/.codeium on Linux/Mac or %USERPROFILE%\.codeium on Windows, then restart VS Code.
• High CPU on first run: Codeium downloads a local model (~1 GB) on first install. The CPU spike is temporary during indexing — wait 5–10 minutes for it to finish before diagnosing a performance problem.

Firewall / proxy issues

Codeium requires outbound HTTPS access to the following endpoints:

• api.codeium.com — completions API for the free and Teams tiers
• enterprise.codeium.com — Enterprise tier (or your self-hosted URL)

If on a corporate proxy, set the https_proxy environment variable before launching VS Code, or add the proxy in VS Code settings under HTTP: Proxy. To reduce the number of outbound API calls, add "codeium.enableSearch": false to your VS Code settings.json.

JetBrains-specific issues

• Plugin not enabled: Go to Settings → Plugins → verify Codeium is enabled and not in an "Error" state. Restart the IDE after enabling.
• Update plugin after IDE major version: After upgrading IntelliJ, PyCharm, or WebStorm to a new major version, check Settings → Plugins → Updates for a compatible Codeium plugin version.
• Sign-in via tool window: Check View → Tool Windows → Codeium for sign-in status. If the Chat tab is missing, sign in through this window first.
• Conflict with AI Assistant: JetBrains' built-in "AI Assistant" may conflict with Codeium completions. Try disabling AI Assistant (Settings → Plugins → AI Assistant) to test whether Codeium completions return.