Tracking which local files Claude changes or deletes

The goal is to automatically keep a simple log of the files Claude creates, edits, or deletes on macOS. The needed record is only the file list, not the exact content changes. The solution should not depend on Claude itself and should not require putting folders into Git.

`fswatch` was suggested as a way to record file changes, but it cannot tell whether Claude changed a file or the person did. That makes it only a partial answer, because a mixed change log is harder to audit than a list of files touched only by Claude. After two cases where Claude behaved unexpectedly, file-change auditing feels important.

Versioned backups already exist through and Backblaze, but backups only help if the deletion is noticed.

Key points

  • The desired tool would log files Claude creates, edits, or deletes on macOS.
  • The log only needs file names, not the exact edits inside each file.
  • The solution should be independent from Claude and should not require Git.
  • `fswatch` can track file changes, but it cannot separate Claude’s actions from human actions.
  • Backups are useful, but they do not help if a deletion goes unnoticed.

Sources covering this story (2)

Read original