[GH-ISSUE #1139] Feature Request: Add temporary conversations (incognito mode) to DeepSeek Chat #715

New issue

Closed

opened 2026-10-26 21:27:25 +00:00 by bsakaguchi · 1 comment

bsakaguchi commented

2026-10-26 21:27:25 +00:00

Owner

Originally created by @lucasrbsouza on GitHub (Mar 6, 2026).
Original GitHub issue: https://github.com/deepseek-ai/DeepSeek-V3/issues/1139

Description

I would like to suggest implementing a temporary conversations feature (or incognito mode) in DeepSeek Chat. Currently, all conversations are saved in the user's history, which may not be ideal in situations where privacy is a priority or when users want to ask quick, disposable questions without cluttering their history.

Motivation

Many users use the chat to:

Test sensitive or personal questions they don't want permanently stored.
Make quick inquiries that don't need to be revisited.
Explore topics without compromising history organization.
Compare responses in different contexts without previous conversations interfering.

Currently, the only way to avoid saving is to use the browser's incognito mode or manually clear the history, which is not practical nor integrated into the product experience.

Proposed Solution

Add a button or option in the interface to start a temporary conversation. This conversation would:

Not be saved in the user's history after closing.
Could be automatically discarded when closing the tab or after a period of inactivity.
Be clearly identified in the interface (e.g., an "eye" or "incognito" icon) to avoid confusion.
During the session, the conversation would work normally, with access to all chat features.

Additional options:

Allow the user to optionally save the conversation to history at the end if desired.
Offer a keyboard shortcut (e.g., Ctrl+Shift+N) to quickly start a temporary conversation.

Benefits

Privacy: Users can ask sensitive questions without worrying about persistent storage.
Organization: Prevents one-off conversations from cluttering the history, making it easier to find important conversations.
Experimentation: Users can test different prompts without affecting the saved context.
Competitiveness: This feature is already present in other chat services (e.g., ChatGPT with temporary mode), making DeepSeek more competitive.

Possible Alternatives

Using browser incognito mode: works but doesn't integrate with the account system and may lose context if the user is logged in.
Manually clearing history: manual process and prone to errors.

Implementation Considerations

The backend should ensure that messages from temporary conversations are not persisted in the database.
The frontend should display a clear indicator that the conversation is temporary.
Consider behavior on page reload: should the temporary conversation be lost or maintained during the browser session? I suggest it be lost on reload to reinforce the temporary nature.

Interface Examples

"+" button next to "New conversation" with option "New temporary conversation".
Toggle in the current conversation header: "Temporary mode" ON/OFF.

Originally created by @lucasrbsouza on GitHub (Mar 6, 2026). Original GitHub issue: https://github.com/deepseek-ai/DeepSeek-V3/issues/1139 ## Description I would like to suggest implementing a **temporary conversations** feature (or incognito mode) in DeepSeek Chat. Currently, all conversations are saved in the user's history, which may not be ideal in situations where privacy is a priority or when users want to ask quick, disposable questions without cluttering their history. ## Motivation Many users use the chat to: - Test sensitive or personal questions they don't want permanently stored. - Make quick inquiries that don't need to be revisited. - Explore topics without compromising history organization. - Compare responses in different contexts without previous conversations interfering. Currently, the only way to avoid saving is to use the browser's incognito mode or manually clear the history, which is not practical nor integrated into the product experience. ## Proposed Solution Add a button or option in the interface to start a **temporary conversation**. This conversation would: - Not be saved in the user's history after closing. - Could be automatically discarded when closing the tab or after a period of inactivity. - Be clearly identified in the interface (e.g., an "eye" or "incognito" icon) to avoid confusion. - During the session, the conversation would work normally, with access to all chat features. Additional options: - Allow the user to optionally save the conversation to history at the end if desired. - Offer a keyboard shortcut (e.g., Ctrl+Shift+N) to quickly start a temporary conversation. ## Benefits - **Privacy**: Users can ask sensitive questions without worrying about persistent storage. - **Organization**: Prevents one-off conversations from cluttering the history, making it easier to find important conversations. - **Experimentation**: Users can test different prompts without affecting the saved context. - **Competitiveness**: This feature is already present in other chat services (e.g., ChatGPT with temporary mode), making DeepSeek more competitive. ## Possible Alternatives - Using browser incognito mode: works but doesn't integrate with the account system and may lose context if the user is logged in. - Manually clearing history: manual process and prone to errors. ## Implementation Considerations - The backend should ensure that messages from temporary conversations are not persisted in the database. - The frontend should display a clear indicator that the conversation is temporary. - Consider behavior on page reload: should the temporary conversation be lost or maintained during the browser session? I suggest it be lost on reload to reinforce the temporary nature. ## Interface Examples - "+" button next to "New conversation" with option "New temporary conversation". - Toggle in the current conversation header: "Temporary mode" ON/OFF.

bsakaguchi closed this issue

2026-10-26 21:27:25 +00:00

bsakaguchi commented

2026-10-26 21:27:26 +00:00

Author

Owner

@rafa-unx commented on GitHub (Jun 30, 2026):

Is it really completed? I don't see the feature in web (chat.deepseek.com).

@rafa-unx commented on GitHub (Jun 30, 2026): Is it really completed? I don't see the feature in web (chat.deepseek.com).