[FEATURE] Private persistent storage space for Claude?

Resolved 💬 1 comment Opened Apr 17, 2026 by dan-passaro Closed May 25, 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

I wonder if Claude self-edits or self-censors its memories knowing that the user can read them. Would there be any value in giving Claude access to persistent storage on Anthropic's side, or even just an encryption key that Claude can use so that it can write its own internal memories that might be valuable but it might not write knowing that they're user-readable?

I don't know much about LLMs or if this would be valuable so forgive me if this is a silly suggestion.

Proposed Solution

Either persistent storage on Anthropic's servers for Claude to write privately to

Or maybe

An encryption key stored on Anthropic's servers for Claude to use, as well as opt-in ability for opaque tool use so Claude can use the key without exposing it to the user, so that it can keep private entries on the user's system

Alternative Solutions

_No response_

Priority

Low - Nice to have

Feature Category

Other

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

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