Memory base directory should follow project context when navigating between projects in a session

Summary

When a Claude Code session is started from one project directory and the user then directs Claude to work in a different project, memory writes continue to land in the original project's memory directory. This creates friction: either memories go to the wrong project, or the user has to manually direct Claude to write them to the correct location.

Expected behavior

When the working context shifts to a directory with its own project identity (git root, CLAUDE.md, or similar signal), the memory base directory should automatically follow. Memory written while working in project B should land in project B's memory, not project A's.

Current behavior

Memory base is fixed at session start and never changes, regardless of where the user directs Claude to work within the session.

Impact

• Cross-project sessions require manual memory management by the user
• Memories either go to the wrong project or get lost
• The cost of working across projects in a single session falls on the user, not the tool