PromptDustCaches
Codeium
Codeium keeps a local codebase embedding index under ~/.codeium/database, plus a config file that can hold an API token (its chat history is largely server-side).
Exposure
- Stores found
- 1
- Holds
- API keys · source code
- Confidence
- likely
Where it writes
1 store in the current signature database. Paths shown for a typical macOS install.
files may hold API keys · source code
- all OSes
~/.codeiumdir
Codeium keeps a local codebase embedding index under ~/.codeium/database, plus a config file that can hold an API token (its chat history is largely server-side).
- Restrict permissions on ~/.codeium; the embedding index is derived from your source.
Source: marketplace.visualstudio.com
What to do about it
PromptDust flags these stores and leaves them in place; cleanup is your call. If a store holds a live secret, rotate the secret first, since deleting the file won’t un-leak a key that already sat in plain text.
For ongoing work, keep sensitive material out of sessions where you can, and prune old transcripts and caches now and then.
This describes where Codeium stores data. Metadata only, never your content. Confidence: likely. Spot a mistake? Tell us.
See if this one’s on your machine.
One pass finds every store, for this tool and the other 51.