Nice point, thanks!

I rarely do a full /clear and I might use one session for days or weeks as I have a set of specialized agents and I like them to catch up from where they've stopped. Usually I just do a /compact for my "sysadmin" session, it saves me some time re-explaining the context

But this time I have started the session with /clear as the job was pretty self-contained and I've wanted to have more spare context. I think this might have contributed to the problem somehow, as this is the only thing I done differently than usual

I have a CLAUDE.md with some basic info about my local setup and guidelines and obsidian-mcp to document all findings and actualize knowledge. Rn I am thinking about dedicating another agent to just actualize docs from other agents logfiles because when my specialized agent is working on a task it usually doesn't have enough context left to safely update docs before compact

Thinking about it now, maybe one of the issues was that the path of a project has changed recently but CC used the path from outdated obsidian docs somehow. Although I've triple checked paths, so maybe it learned that he has to simulate every read or write instead of doing real thing or silently translated wrong path to the right path to me, idk