PromptDustConfig & secrets · Transcripts
Gemini CLI
Gemini CLI keeps per-project chat history and tool I/O under ~/.gemini/tmp, keyed by a hash of the project path.
Exposure
- Stores found
- 2
- Holds
- API keys · personal data · source code
- Confidence
- likely
Where it writes
2 stores in the current signature database. Paths shown for a typical macOS install.
files may hold personal data · source code
- all OSes
~/.gemini/tmpdir
Gemini CLI keeps per-project chat history and tool I/O under ~/.gemini/tmp, keyed by a hash of the project path.
- Prune ~/.gemini/tmp to reduce local conversation retention.
Source: github.com
JSON may hold API keys
- all OSes
~/.gemini/oauth_creds.json
Gemini CLI stores Google OAuth tokens in ~/.gemini/oauth_creds.json.
- Keep ~/.gemini off cloud sync and restrict its permissions.
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 Gemini 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.