mirror of
https://github.com/deepseek-ai/DeepSeek-R1.git
synced 2026-11-05 00:47:42 +00:00
[GH-ISSUE #854] Subject: Feature Request: Cross‑Chat Persistent Memory #706
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
deepseek-ai/DeepSeek-R1#706
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @zafarhussainzh-sketch on GitHub (Jun 7, 2026).
Original GitHub issue: https://github.com/deepseek-ai/DeepSeek-R1/issues/854
Dear DeepSeek Team,
First, thank you for building an extraordinary platform. The depth of reasoning, the generous free tier, and the consistent reliability are genuinely impressive — you've created something that users like me depend on daily. I appreciate the hard work that goes into every release.
I’d like to suggest a feature that would make a profound difference for many of your users, especially those juggling complex, multi‑step workflows.
The Scenario
A user runs several separate chats, each for a different purpose — say, one for project planning, another for research, a third for writing. Each chat maintains its own context and logs, which is perfect. But often, an update in one chat (like a change in project status or a new piece of research) needs to be reflected in the others. Currently, the only way to do this is to manually copy information from one chat and paste it into another. That’s slow, breaks concentration, and eats up tokens with repeated context‑setting.
The Request
Would it be possible to introduce a user‑controlled, cross‑chat persistent global memory space or access to the specific chats persistent memory by prompts? Something like a small shared notepad where a user can store key data — plain text, logs, or status updates — that other chats can read before generating a response. This would be entirely opt‑in, with no automatic sharing. Users would explicitly save information to the shared space and grant specific chats permission to access it.
The Impact
Seamless workflows: A change made in one chat is instantly available in another. No more manual sync.
Token efficiency: Less repetitive background context means more of the conversation’s token budget goes to actual work.
Better user experience: DeepSeek would feel less like isolated conversations and more like a connected, intelligent workspace — an assistant that truly remembers across sessions.
I believe this would place DeepSeek ahead of the curve in the personal‑AI assistant market. Even a basic implementation — a single, shared text blob that chats can read — would be transformative.
Thank you for considering this. I’m excited to see where you take the platform next.
Sincerely,
Zafar Hussain.
@hiSandog commented on GitHub (Jun 28, 2026):
Persistent memory would need a very clear user-control model to avoid surprising people. If this becomes a product proposal, I would suggest scoping it around opt-in memories with a visible list, per-chat enable/disable, and easy deletion/export. That keeps the feature useful for continuity while making the privacy and context-boundary behavior understandable.
@github-actions[bot] commented on GitHub (Jul 29, 2026):
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe this issue is still relevant, please leave a comment to keep it open. Thank you for your contributions!
@github-actions[bot] commented on GitHub (Aug 13, 2026):
false