[FEATURE] Feature request: opt-in global memory shared across projects

Status Open
Maintainer reply None cached
Activity 1 comment · opened Aug 28, 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

Problem
Claude Code's memory system currently scopes each project's memory files to that project's working directory (.claude/projects/<project-path>/memory/). This means working-style preferences and feedback I give Claude have to be re-taught from scratch in every new project, even when they're general and not tied to any specific codebase.

Proposed Solution

Proposed solution
Support an optional global memory location (e.g. ~/.claude/memory/global/) that's loaded in every project alongside the project-specific memory, for preferences that aren't tied to one codebase. Project-specific memory (architecture decisions, project context) would stay scoped as it is today.

Alternative Solutions

Alternative
A /memory promote <name> command that moves an existing project-scoped memory entry into the global scope, for cases where a preference started out project-specific and turned out to apply more broadly.

Priority

High - Significant impact on productivity

Feature Category

Configuration and settings

Use Case Example

An overall example is the way I work with Claude, and I want it to remember that approach in every project.

My current workaround:
I keep a manual preferences file outside any project and ask Claude to read and remember it at the start of each new project. This works, but it's a manual step I have to repeat every time, and it's easy to forget.

Additional Context

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗