PromptDustEmbeddings
Cody
Cody (Sourcegraph) stores its symf local code-search index (derived from your source) under this globalStorage directory; chat history persists in the shared VS Code state store, covered separately.
Exposure
- Stores found
- 1
- Holds
- source code
- Confidence
- likely
Where it writes
1 store in the current signature database. Paths shown for a typical macOS install.
files may hold source code
- macOS
~/Library/Application Support/Code/User/globalStorage/sourcegraph.cody-aidir - macOS
~/Library/Application Support/Cursor/User/globalStorage/sourcegraph.cody-aidir - Linux
~/.config/Code/User/globalStorage/sourcegraph.cody-aidir - Linux
~/.config/Cursor/User/globalStorage/sourcegraph.cody-aidir - Windows
~/AppData/Roaming/Code/User/globalStorage/sourcegraph.cody-aidir - Windows
~/AppData/Roaming/Cursor/User/globalStorage/sourcegraph.cody-aidir
Cody (Sourcegraph) stores its symf local code-search index (derived from your source) under this globalStorage directory; chat history persists in the shared VS Code state store, covered separately.
- This is a derived source index; Cody chat lives in the VS Code global state store. Scan other VS Code forks with --path.
Source: sourcegraph.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 Cody 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.