Catalog/Aider

Transcripts

Aider

Aider writes chat history into the working directory, where it frequently lands inside a git repository.

Aider Linux · macOS plaintext

Exposure

High
Stores found
1
Holds
API keys · personal data · source code
Confidence
unverified

Where it writes

1 store in the current signature database. Paths shown for a typical macOS install.

Transcripts high

plaintext may hold API keys · personal data · source code

  • all OSes ~/Projects/**/.aider.chat.history.md
  • all OSes ~/projects/**/.aider.chat.history.md
  • all OSes ~/Code/**/.aider.chat.history.md
  • all OSes ~/code/**/.aider.chat.history.md
  • all OSes ~/src/**/.aider.chat.history.md
  • all OSes ~/dev/**/.aider.chat.history.md
  • all OSes ~/work/**/.aider.chat.history.md

Aider writes chat history into the working directory, where it frequently lands inside a git repository.

  • Add .aider.chat.history.md and .aider.input.history to your .gitignore.
  • For projects outside the common code roots, run a scan with --path <dir>.

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 Aider stores data. Metadata only, never your content. Confidence: unverified. 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.