The best mitigation I've found against this is training Claude to collate what it does within the project dir, specifically a CLAUDE.md vision file and .claude/changelog that documents the changes it makes. The biggest pain point though is remembering to force it to do that between sessions (man is that contextual memory unreliable sometimes).

▲

Schiendelman 4 hours ago | parent [-]

Oh yeah - it commonly doesn't update my BACKLOG.md after shipping something. It tends to catch itself on the next set of work, but sometimes I have it clean up based on recent commits.

	▲	tstrimple 25 minutes ago \| parent [-]
		Have you tried using hooks? I have a similar changelog except I write it to a SQLite database for searchability across all my sessions. I use the Stop/StopFailure hooks and it reliably writes to the change log. I used to just use CLAUDE.md instructions for this, but as you've experienced it's not completely reliable. https://code.claude.com/docs/en/hooks