PromptDustTranscripts
Grok CLI
The grok-cli agent stores conversation history and tool executions in ~/.grok/grok.db (the ~/.grok directory is shared with other Grok tools).
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.
SQLite may hold personal data · source code
- all OSes
~/.grok/grok.db
The grok-cli agent stores conversation history and tool executions in ~/.grok/grok.db (the ~/.grok directory is shared with other Grok tools).
- Prune ~/.grok/grok.db or remove it to clear local history.
Source: github.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 Grok CLI 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.