Where Does Codeium Store Config and Data?
Codeium stores its API key in a .codeium folder in your home directory, with the language server database beside it. Editor state stays in VS Code storage.
Last updated
Codeium divides its footprint between two owners. The language server owns a .codeium folder in your home directory with the API key config plus embedding databases. The editor extension owns its slice of VS Code globalStorage for chat and UI state.
On plain setups the home folder path is literally ~/.codeium. XDG-aware installs may relocate parts under local share or config, which explains the duplicate-looking trees people report. When something breaks, check config.json first for auth, the database folder second for bloat, and the editor storage third for UI state.
Where Codeium stores this, by platform
%USERPROFILE%\.codeium\config.json
API key config plus language server database with sqlite companions. XDG variables can relocate parts of this tree, so check local share when the home folder looks thin. Editor chat state lives separately in VS Code globalStorage.
~/.codeium/config.json
Same home-dir config and database layout. The Vim plugin documents the XDG fallback chain explicitly, which is the clearest spec for where each piece lands when variables are set.
~/.codeium/config.json
Same home-dir layout, honoring $XDG_DATA_HOME and $XDG_CONFIG_HOME when set. Unset variables fall back to ~/.codeium and ~/.local/share per the base directory spec. Database sqlite files rebuild after deletion.
Frequently asked questions
Where is my Codeium API key file?
Open ~/.codeium/config.json (on Windows %USERPROFILE%\.codeium\config.json). It holds the apiKey written at login. Recreate it by logging in again if the file is missing. The folder also respects XDG variables on setups that define them.
What is taking so much space in .codeium?
Look under ~/.codeium/database for versioned embedding databases with sqlite, shm and wal companions. Those files can grow large and are safe to delete. They rebuild from your code on next index. Keep config.json and drop the database folder when disk space matters.
Where does the Codeium VS Code extension keep state?
Check the VS Code globalStorage state database plus the extension's own folder there. Chat and auth state beyond config.json lives in the editor layer. The .codeium folder covers the language server side only, so both halves matter when debugging login loops.
Notice an outdated path? Let us know.