PromptDustTranscripts
Amazon Q Developer CLI
The Amazon Q CLI keeps conversations plus SSO/Builder-ID auth and credential state together in a single local SQLite file (data.sqlite3).
Exposure
- Stores found
- 1
- Holds
- API keys · 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 API keys · personal data · source code
- macOS
~/Library/Application Support/amazon-q/data.sqlite3 - Linux
~/.local/share/amazon-q/data.sqlite3 - Windows
~/AppData/Local/amazon-q/data.sqlite3
The Amazon Q CLI keeps conversations plus SSO/Builder-ID auth and credential state together in a single local SQLite file (data.sqlite3).
- Keep the amazon-q data directory off cloud sync; the database holds both chats and credentials.
Source: docs.aws.amazon.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 Amazon Q Developer 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.