[FEATURE] Auto Memory Scoping Limitation

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Currently, Claude Code's auto memory writes only to ~/.claude/CLAUDE.md (user-level), meaning memories accumulate globally across all projects rather than being scoped to the project where they were learned. A project-level auto memory option would be more useful for keeping context relevant and potentially shareable across teams.

Proposed Solution

Introduce an autoMemoryScope setting that lets users control where auto memory is written. By default it keeps the current global behavior (~/.claude/CLAUDE.md), but when set to project, Claude writes memories to .claude/memory/ inside the project directory instead. A both option could also be supported for users who want memories captured at both levels.
This gives teams the flexibility to keep project-specific context isolated, optionally commit it to version control for shared team knowledge, and prevent unrelated project memories from bleeding into each other. CI environments could also benefit by scoping memory to the project rather than relying on a developer's global home folder.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

Other

Use Case Example

_No response_

Additional Context

_No response_