[GH-ISSUE #1049] A function to search previous chats #647

New issue

Closed

opened 2026-10-26 21:24:42 +00:00 by bsakaguchi · 10 comments

bsakaguchi commented 2026-10-26 21:24:42 +00:00

Owner

Copy link

Originally created by @TheRealRWJ on GitHub (Dec 7, 2025).
Original GitHub issue: https://github.com/deepseek-ai/DeepSeek-V3/issues/1049

Is your feature request related to a problem? Please describe.
No not really, BUT I do think it is a problem loosing time to manually scrolling through my previous chats

Describe the solution you'd like
I Like a function to search the titles and or content of my previous chats

Describe alternatives you've considered
Scrolling through my previous chats is not really a valid option

Additional context
Just a search field to search the chat titles and a button to search the content too would be a great help
The advantage of this is I do not have to ask the same question again so do not use extra resources

Originally created by @TheRealRWJ on GitHub (Dec 7, 2025). Original GitHub issue: https://github.com/deepseek-ai/DeepSeek-V3/issues/1049 **Is your feature request related to a problem? Please describe.** No not really, BUT I do think it is a problem loosing time to manually scrolling through my previous chats **Describe the solution you'd like** I Like a function to search the titles and or content of my previous chats **Describe alternatives you've considered** Scrolling through my previous chats is not really a valid option **Additional context** Just a search field to search the chat titles and a button to search the content too would be a great help The advantage of this is I do not have to ask the same question again so do not use extra resources

bsakaguchi 2026-10-26 21:24:42 +00:00

• closed this issue
• added the
  stale
  closed-as-stale
  labels

bsakaguchi commented 2026-10-26 21:24:44 +00:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Jan 7, 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!

<!-- gh-comment-id:3716817992 --> @github-actions[bot] commented on GitHub (Jan 7, 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!

bsakaguchi commented 2026-10-26 21:24:44 +00:00

Author

Owner

Copy link

@TheRealRWJ commented on GitHub (Jan 7, 2026):

Please add this option

<!-- gh-comment-id:3720040978 --> @TheRealRWJ commented on GitHub (Jan 7, 2026): Please add this option

bsakaguchi commented 2026-10-26 21:24:44 +00:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Feb 7, 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!

<!-- gh-comment-id:3863126785 --> @github-actions[bot] commented on GitHub (Feb 7, 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!

bsakaguchi commented 2026-10-26 21:24:45 +00:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Feb 23, 2026):

false

<!-- gh-comment-id:3941997986 --> @github-actions[bot] commented on GitHub (Feb 23, 2026): false

bsakaguchi commented 2026-10-26 21:24:45 +00:00

Author

Owner

Copy link

@giunot commented on GitHub (May 4, 2026):

I strongly support this feature. I manage complex medical data across multiple conversations, and the inability to search past chats forces me to re-enter critical information manually. This would save hours of work and reduce errors. Please prioritize this. Thank you.

<!-- gh-comment-id:4371142140 --> @giunot commented on GitHub (May 4, 2026): I strongly support this feature. I manage complex medical data across multiple conversations, and the inability to search past chats forces me to re-enter critical information manually. This would save hours of work and reduce errors. Please prioritize this. Thank you.

bsakaguchi commented 2026-10-26 21:24:46 +00:00

Author

Owner

Copy link

@qingkong66 commented on GitHub (May 4, 2026):

@giunot Thank you for speaking up on this closed issue.

You're right to keep asking. A bot clicking "close" is not the same as the team saying "no." And your use case — complex medical data across multiple conversations — is exactly why this feature matters.

Manual re-entry of critical information is not just time‑consuming. In clinical scenarios, it's also an error vector. That alone makes search a safety-adjacent feature, not a convenience.

We've decided to include #1049 in the second‑phase feedback submission pool, with a clear note: closed by bot, but users keep asking — clinical user evidence attached.

Your comment has been archived alongside #1121 (persistent memory) as a paired requirement. If both were implemented, they would fundamentally change how medical data is managed inside this platform.

The next batch will go to the official team. No promises on their side, but the issue will not be silently dropped.

Thank you for pushing on this.

<!-- gh-comment-id:4375200933 --> @qingkong66 commented on GitHub (May 4, 2026): @giunot Thank you for speaking up on this closed issue. You're right to keep asking. A bot clicking "close" is not the same as the team saying "no." And your use case — complex medical data across multiple conversations — is exactly why this feature matters. Manual re-entry of critical information is not just time‑consuming. In clinical scenarios, it's also an error vector. That alone makes search a safety-adjacent feature, not a convenience. We've decided to include #1049 in the second‑phase feedback submission pool, with a clear note: closed by bot, but users keep asking — clinical user evidence attached. Your comment has been archived alongside #1121 (persistent memory) as a paired requirement. If both were implemented, they would fundamentally change how medical data is managed inside this platform. The next batch will go to the official team. No promises on their side, but the issue will not be silently dropped. Thank you for pushing on this.

bsakaguchi commented 2026-10-26 21:24:46 +00:00

Author

Owner

Copy link

@giunot commented on GitHub (May 5, 2026):

Thank you for this detailed and honest update. I'm glad to hear that #1049 has been rescued from the bot closure, and that #1121 is being actively worked on. I'll keep using DeepSeek for my clinical work and will test these features as soon as they become available. Grateful for your transparency

A small but important clarification to my previous comments: I am not a doctor. I am a patient managing my own complex medical history because the healthcare system in my country no longer keeps track of it effectively. I use DeepSeek to fill that gap — to prevent, not just to react. My request for persistent memory and cross-chat search comes from a place of necessity, not convenience.
Thank you for understanding

5 mag 2026, 01:13 da @.***:

qingkong66> left a comment > (deepseek-ai/DeepSeek-V3#1049) https://github.com/deepseek-ai/DeepSeek-V3/issues/1049#issuecomment-4375200933

@giunot https://github.com/giunot> Thank you for speaking up on this closed issue.

You're right to keep asking. A bot clicking "close" is not the same as the team saying "no." And your use case — complex medical data across multiple conversations — is exactly why this feature matters.

Manual re-entry of critical information is not just time‑consuming. In clinical scenarios, it's also an error vector. That alone makes search a safety-adjacent feature, not a convenience.

We've decided to include > #1049 https://github.com/deepseek-ai/DeepSeek-V3/issues/1049> in the second‑phase feedback submission pool, with a clear note: closed by bot, but users keep asking — clinical user evidence attached.

Your comment has been archived alongside > #1121 https://github.com/deepseek-ai/DeepSeek-V3/issues/1121> (persistent memory) as a paired requirement. If both were implemented, they would fundamentally change how medical data is managed inside this platform.

The next batch will go to the official team. No promises on their side, but the issue will not be silently dropped.

Thank you for pushing on this.

—
Reply to this email directly, > view it on GitHub https://github.com/deepseek-ai/DeepSeek-V3/issues/1049#issuecomment-4375200933> , or > unsubscribe https://github.com/notifications/unsubscribe-auth/CCDHTUNPXAXCO7R4URCRM3D4ZEPYFAVCNFSM6AAAAACOJHEQLKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DGNZVGIYDAOJTGM> .
Triage notifications on the go with GitHub Mobile for > iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or > Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub> .
You are receiving this because you were mentioned.> Message ID: > <deepseek-ai/DeepSeek-V3/issues/1049/4375200933> @> github> .> com>

<!-- gh-comment-id:4377331770 --> @giunot commented on GitHub (May 5, 2026): Thank you for this detailed and honest update. I'm glad to hear that #1049 has been rescued from the bot closure, and that #1121 is being actively worked on. I'll keep using DeepSeek for my clinical work and will test these features as soon as they become available. Grateful for your transparency A small but important clarification to my previous comments: I am not a doctor. I am a patient managing my own complex medical history because the healthcare system in my country no longer keeps track of it effectively. I use DeepSeek to fill that gap — to prevent, not just to react. My request for persistent memory and cross-chat search comes from a place of necessity, not convenience. Thank you for understanding 5 mag 2026, 01:13 da ***@***.***: > qingkong66> left a comment > (deepseek-ai/DeepSeek-V3#1049) <https://github.com/deepseek-ai/DeepSeek-V3/issues/1049#issuecomment-4375200933> > > @giunot <https://github.com/giunot>> Thank you for speaking up on this closed issue. > > > You're right to keep asking. A bot clicking "close" is not the same as the team saying "no." And your use case — complex medical data across multiple conversations — is exactly why this feature matters. > > > Manual re-entry of critical information is not just time‑consuming. In clinical scenarios, it's also an error vector. That alone makes search a safety-adjacent feature, not a convenience. > > > We've decided to include > #1049 <https://github.com/deepseek-ai/DeepSeek-V3/issues/1049>> in the second‑phase feedback submission pool, with a clear note: closed by bot, but users keep asking — clinical user evidence attached. > > > Your comment has been archived alongside > #1121 <https://github.com/deepseek-ai/DeepSeek-V3/issues/1121>> (persistent memory) as a paired requirement. If both were implemented, they would fundamentally change how medical data is managed inside this platform. > > > The next batch will go to the official team. No promises on their side, but the issue will not be silently dropped. > > > Thank you for pushing on this. > > > > — > Reply to this email directly, > view it on GitHub <https://github.com/deepseek-ai/DeepSeek-V3/issues/1049#issuecomment-4375200933>> , or > unsubscribe <https://github.com/notifications/unsubscribe-auth/CCDHTUNPXAXCO7R4URCRM3D4ZEPYFAVCNFSM6AAAAACOJHEQLKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DGNZVGIYDAOJTGM>> . > Triage notifications on the go with GitHub Mobile for > iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>> or > Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>> . > You are receiving this because you were mentioned.> Message ID: > <deepseek-ai/DeepSeek-V3/issues/1049/4375200933> @> github> .> com> > > >

bsakaguchi commented 2026-10-26 21:24:46 +00:00

Author

Owner

Copy link

@giunot commented on GitHub (May 22, 2026):

La funzione di ricerca trasversale è arrivata con l'aggiornamento dell'11 maggio 2026.
Grazie a chi ha ascoltato.
giunot

<!-- gh-comment-id:4520072413 --> @giunot commented on GitHub (May 22, 2026): La funzione di ricerca trasversale è arrivata con l'aggiornamento dell'11 maggio 2026. Grazie a chi ha ascoltato. giunot

bsakaguchi commented 2026-10-26 21:24:46 +00:00

Author

Owner

Copy link

@qingkong66 commented on GitHub (May 22, 2026):

@giunot

Thank you for this update — and for your earlier clarification that you are a patient managing your own history, not a doctor. That context matters.

The cross-chat search arriving on May 11 is real progress. One step toward the persistent memory you and others have requested (#1121, #1293).

Not the full solution yet, but a meaningful one.

<!-- gh-comment-id:4521022849 --> @qingkong66 commented on GitHub (May 22, 2026): @giunot Thank you for this update — and for your earlier clarification that you are a patient managing your own history, not a doctor. That context matters. The cross-chat search arriving on May 11 is real progress. One step toward the persistent memory you and others have requested (#1121, #1293). Not the full solution yet, but a meaningful one.

bsakaguchi commented 2026-10-26 21:24:47 +00:00

Author

Owner

Copy link

@giunot commented on GitHub (May 22, 2026):

Thank you, qingkong66.
I'll keep using grateful what we have now, and hoping for what comes next.

22 mag 2026, 19:12 da @.***:

qingkong66> left a comment > (deepseek-ai/DeepSeek-V3#1049) https://github.com/deepseek-ai/DeepSeek-V3/issues/1049#issuecomment-4521022849

@giunot https://github.com/giunot

Thank you for this update — and for your earlier clarification that you are a patient managing your own history, not a doctor. That context matters.

The cross-chat search arriving on May 11 is real progress. One step toward the persistent memory you and others have requested (> #1121 https://github.com/deepseek-ai/DeepSeek-V3/issues/1121> , > #1293 https://github.com/deepseek-ai/DeepSeek-V3/issues/1293> ).

Not the full solution yet, but a meaningful one.

—
Reply to this email directly, > view it on GitHub https://github.com/deepseek-ai/DeepSeek-V3/issues/1049#issuecomment-4521022849> , or > unsubscribe https://github.com/notifications/unsubscribe-auth/CCDHTUPUQSMQUWMXGE76WXD44CDBRAVCNFSM6AAAAACOJHEQLKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DKMRRGAZDEOBUHE> .
Triage notifications on the go with GitHub Mobile for > iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or > Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub> .
You are receiving this because you were mentioned.> Message ID: > <deepseek-ai/DeepSeek-V3/issues/1049/4521022849> @> github> .> com>

<!-- gh-comment-id:4521384608 --> @giunot commented on GitHub (May 22, 2026): Thank you, qingkong66. I'll keep using grateful what we have now, and hoping for what comes next. 22 mag 2026, 19:12 da ***@***.***: > qingkong66> left a comment > (deepseek-ai/DeepSeek-V3#1049) <https://github.com/deepseek-ai/DeepSeek-V3/issues/1049#issuecomment-4521022849> > > @giunot <https://github.com/giunot> > > > Thank you for this update — and for your earlier clarification that you are a patient managing your own history, not a doctor. That context matters. > > > The cross-chat search arriving on May 11 is real progress. One step toward the persistent memory you and others have requested (> #1121 <https://github.com/deepseek-ai/DeepSeek-V3/issues/1121>> , > #1293 <https://github.com/deepseek-ai/DeepSeek-V3/issues/1293>> ). > > > Not the full solution yet, but a meaningful one. > > > > — > Reply to this email directly, > view it on GitHub <https://github.com/deepseek-ai/DeepSeek-V3/issues/1049#issuecomment-4521022849>> , or > unsubscribe <https://github.com/notifications/unsubscribe-auth/CCDHTUPUQSMQUWMXGE76WXD44CDBRAVCNFSM6AAAAACOJHEQLKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DKMRRGAZDEOBUHE>> . > Triage notifications on the go with GitHub Mobile for > iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>> or > Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>> . > You are receiving this because you were mentioned.> Message ID: > <deepseek-ai/DeepSeek-V3/issues/1049/4521022849> @> github> .> com> > > >

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

main

v1.0.0

Labels

Clear labels   

closed-as-stale

  

enhancement

  

question

  

spam

  

stale

No labels

closed-as-stale

enhancement

question

spam

stale

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

deepseek-ai/DeepSeek-V3#647

No description provided.