[GH-ISSUE #64] Feature Request: Add Share Functionality to Chats for Easy Sharing #53

New issue

Closed

opened 2026-10-26 21:12:23 +00:00 by bsakaguchi · 3 comments

bsakaguchi commented

2026-10-26 21:12:23 +00:00

Owner

Originally created by @prdai on GitHub (Jan 24, 2025).
Original GitHub issue: https://github.com/deepseek-ai/DeepSeek-R1/issues/64

🚀 Problem Statement

Currently, users cannot directly share DeepSeek-R1 chat conversations with others, making collaboration or knowledge-sharing cumbersome. Manually copying/pasting chat content is time-consuming and loses formatting/context.

💡 Proposed Solution

Implement a "Share" button/feature within chats to allow users to:

Generate a shareable link (public or private) to the entire chat thread.
Export chats as text, PDF, or Markdown for offline sharing.
Integrate with platforms (e.g., social media, email, messaging apps) for one-click sharing.
Add optional privacy controls (e.g., password protection, expiration dates for links).

🌟 Use Cases

Sharing technical solutions or troubleshooting steps with colleagues.
Distributing educational/helpdesk interactions.
Showcasing creative or coding outputs from DeepSeek-R1 on forums or social platforms.

📝 Additional Context

Similar features exist in tools like ChatGPT (share links) and Google Docs.
This would improve collaboration, user engagement, and DeepSeek-R1’s visibility.

Originally created by @prdai on GitHub (Jan 24, 2025). Original GitHub issue: https://github.com/deepseek-ai/DeepSeek-R1/issues/64 ### 🚀 Problem Statement Currently, users cannot directly share DeepSeek-R1 chat conversations with others, making collaboration or knowledge-sharing cumbersome. Manually copying/pasting chat content is time-consuming and loses formatting/context. ### 💡 Proposed Solution Implement a **"Share" button/feature** within chats to allow users to: 1. **Generate a shareable link** (public or private) to the entire chat thread. 2. **Export chats** as text, PDF, or Markdown for offline sharing. 3. **Integrate with platforms** (e.g., social media, email, messaging apps) for one-click sharing. 4. Add optional **privacy controls** (e.g., password protection, expiration dates for links). ### 🌟 Use Cases - Sharing technical solutions or troubleshooting steps with colleagues. - Distributing educational/helpdesk interactions. - Showcasing creative or coding outputs from DeepSeek-R1 on forums or social platforms. ### 📝 Additional Context - Similar features exist in tools like ChatGPT (share links) and Google Docs. - This would improve collaboration, user engagement, and DeepSeek-R1’s visibility.

bsakaguchi closed this issue

2026-10-26 21:12:24 +00:00

bsakaguchi commented

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

Author

Owner

@mowentian commented on GitHub (Jan 26, 2025):

Thank you for your suggestion. It has been forwarded to the product manager. The session sharing feature is indeed part of our plan.
https://github.com/deepseek-ai/DeepSeek-V3/issues/308

@mowentian commented on GitHub (Jan 26, 2025): Thank you for your suggestion. It has been forwarded to the product manager. The session sharing feature is indeed part of our plan. https://github.com/deepseek-ai/DeepSeek-V3/issues/308

bsakaguchi commented

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

Author

Owner

@Dhananjay-JSR commented on GitHub (Feb 16, 2025):

Just in case someone needs to share the chat , You can use this extension to share your session publically or privately

https://github.com/Dhananjay-JSR/deep-sync

@Dhananjay-JSR commented on GitHub (Feb 16, 2025): Just in case someone needs to share the chat , You can use this extension to share your session publically or privately https://github.com/Dhananjay-JSR/deep-sync

bsakaguchi commented

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

Author

Owner

@wpbullet commented on GitHub (Sep 8, 2025):

Yea this is necessary and has caused so much confusion when I was trying to share the link. It drove me insane.

@wpbullet commented on GitHub (Sep 8, 2025): Yea this is necessary and has caused so much confusion when I was trying to share the link. It drove me insane.