claude-code - 💡(How to fix) Fix Universal persistent memory across all Claude surfaces [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#58755Fetched 2026-05-14 03:40:19
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
Participants
Timeline (top)
labeled ×2
RAW_BUFFERClick to expand / collapse

Preflight Checklist

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

Problem Statement

Lack of Universal Memory per User/Team

Proposed Solution

Hi Anthropic team,

I'd like to suggest a feature that I think would significantly improve the experience for power users: universal, persistent memory that works across all Claude interfaces — claude.ai (web), Claude desktop (Cowork), Claude Code (CLI/VPS), and the VS Code extension. The problem today: Each interface has its own isolated context. A user who works across multiple environments has to re-explain their preferences, projects, and background in every single session. This creates friction and limits how useful Claude can be as a long-term assistant. The proposal: A unified memory layer — a structured file (e.g. JSON or Markdown) containing user preferences, ongoing projects, and key facts — that every Claude interface can read from and write to. The key design idea — user-defined storage: Rather than forcing a single centralized store, let users choose where their memory lives: Anthropic cloud (zero-config default) Their own S3/R2/Blob storage (for enterprise/compliance needs) A self-hosted server or VPS A private Git repository (with built-in versioning and history) This approach respects privacy, satisfies compliance requirements, and gives technical users full control. Why this matters: For developers and professionals working across web, desktop, and CLI environments simultaneously, this would transform Claude from a per-session tool into a genuine long-term collaborator.

Alternative Solutions

No response

Priority

High - Significant impact on productivity

Feature Category

CLI commands and flags

Use Case Example

No response

Additional Context

No response

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Universal persistent memory across all Claude surfaces [1 participants]