This resonates. I've been running 70+ Claude Code sessions across different projects and the context loss between sessions is brutal. My workaround has been CLAUDE.md files that get auto-loaded, plus activity logs in each project. The QMD indexing approach is clever - semantic search over past sessions could save a lot of 're-explaining the architecture' time. How does it handle when you've changed direction mid-project?
This resonates. I've been running 70+ Claude Code sessions across different projects and the context loss between sessions is brutal. My workaround has been CLAUDE.md files that get auto-loaded, plus activity logs in each project. The QMD indexing approach is clever - semantic search over past sessions could save a lot of 're-explaining the architecture' time. How does it handle when you've changed direction mid-project?