[FEATURE] autoMemoryDirectory should support local repo storage

Status Open
Maintainer reply None cached
Activity 5 comments · opened Aug 18, 2026

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

Only supports absolute paths and as such can not easily source control your memory files.

https://github.com/anthropics/claude-code/issues/33535
https://github.com/anthropics/claude-code/issues/34146
https://github.com/anthropics/claude-code/issues/36636

Proposed Solution

Allow setting relative paths or including env vars.

Alternative Solutions

Anything, just make it easy to use.

Priority

High - Significant impact on productivity

Feature Category

Configuration and settings

Use Case Example

  1. Save memories
  2. Commit memories
  3. Share and retain memories

Additional Context

_No response_

View original on GitHub ↗

3 Comments

gmantova · 21 days ago

Still applies on 2.1.280. A relative autoMemoryDirectory fails the resolver's isAbsolute check and memory silently falls back to ~/.claude/projects/<sanitized-cwd>/memory/, even though project and local settings are now honored after the workspace trust prompt (the docs: the value "must be an absolute path or start with ~/").

Resolving a relative value against the project root (and rejecting one that escapes it with ..), or expanding ${CLAUDE_PROJECT_DIR} as hooks already do, would make memory committable with a single line in .claude/settings.json. Until then, a wrapper that computes the project root at launch and passes an absolute path through --settings works on Windows, macOS and Linux: https://github.com/anthropics/claude-code/issues/25739#issuecomment-5744598122

mryellow · 21 days ago

Can we prevent github-actions bot from locking this thread as it has done every other time it has been reported?

Or perhaps at least have it post so we can come back and revive the thread before it gets locked as "stale"?

gmantova · 20 days ago
Can we prevent github-actions bot from locking this thread as it has done every other time it has been reported? Or perhaps at least have it post so we can come back and revive the thread before it gets locked as "stale"?

We need to collect more upvotes (at least 20 it seems). or keep posting comments. Probably every two weeks max.

I'll try to set up a remainder to ask claude to prevent another claude from closing the claude bug.

Showing cached comments. Read the full discussion on GitHub ↗