PromptDustConfig & secrets · Transcripts
Codex CLI
Codex CLI records resumable conversation rollouts as JSONL under ~/.codex/sessions.
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
~/.codex/sessionsdir
Codex CLI records resumable conversation rollouts as JSONL under ~/.codex/sessions.
- Set CODEX_HOME to relocate the store, or prune ~/.codex/sessions to limit retention.
Source: github.com
JSON may hold API keys
- all OSes
~/.codex/auth.json
Codex CLI can store an OpenAI API key or ChatGPT OAuth tokens in ~/.codex/auth.json (unless using the OS keyring).
- Ensure ~/.codex/auth.json is not world-readable and not cloud-synced.
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 Codex 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.