PromptDustTranscripts
Roo Code
Roo Code (a Cline fork) stores verbatim agent task history as JSON under its globalStorage tasks directory.
Exposure
- Stores found
- 1
- Holds
- personal data · source code
- Confidence
- likely
Where it writes
1 store in the current signature database. Paths shown for a typical macOS install.
files may hold personal data · source code
- macOS
~/Library/Application Support/Code/User/globalStorage/rooveterinaryinc.roo-cline/tasksdir - macOS
~/Library/Application Support/Cursor/User/globalStorage/rooveterinaryinc.roo-cline/tasksdir - Linux
~/.config/Code/User/globalStorage/rooveterinaryinc.roo-cline/tasksdir - Linux
~/.config/Cursor/User/globalStorage/rooveterinaryinc.roo-cline/tasksdir - Windows
~/AppData/Roaming/Code/User/globalStorage/rooveterinaryinc.roo-cline/tasksdir - Windows
~/AppData/Roaming/Cursor/User/globalStorage/rooveterinaryinc.roo-cline/tasksdir
Roo Code (a Cline fork) stores verbatim agent task history as JSON under its globalStorage tasks directory.
- Delete old tasks from Roo Code's history; if you set a custom storage path, or use another VS Code fork, scan it with --path.
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 Roo Code 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.