Config & secrets · Transcripts
aichat
aichat saves named sessions as YAML under its config directory (and appends saved chats to messages.md).
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
- macOS
~/Library/Application Support/aichat/sessionsdir - Linux
~/.config/aichat/sessionsdir - Windows
~/AppData/Roaming/aichat/sessionsdir
aichat saves named sessions as YAML under its config directory (and appends saved chats to messages.md).
- Prune the aichat sessions directory and messages.md to limit retention.
Source: github.com
plaintext may hold API keys
- macOS
~/Library/Application Support/aichat/config.yaml - Linux
~/.config/aichat/config.yaml - Windows
~/AppData/Roaming/aichat/config.yaml
aichat stores provider API keys in its config.yaml.
- Restrict permissions on the aichat config directory and keep it off cloud sync.
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 aichat 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.