[GH-ISSUE #1058] Client-side Markdown Preview / Rendering for User Messages in Web Chat #652

New issue

Closed

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

bsakaguchi commented

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

Owner

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

Problem Statement:
Currently, users cannot format their messages using Markdown syntax (like code blocks with triple backticks) in the DeepSeek web chat. While the assistant's responses are beautifully rendered with proper code formatting and syntax highlighting, user input is displayed as plain text. This creates a disjointed and less productive experience, especially when discussing technical topics, sharing code snippets, or asking for debugging help.

Alternatives that I have considered:

Sending the code without formatting: This is the current "workaround", but it greatly reduces readability, especially for multi-line code.
Using external services: Creating snippets on third-party platforms (like GitHub Gist) and sending links. This disrupts the workflow and requires additional actions.

Proposed Solution:
Implement client-side Markdown rendering for user messages before they are sent or live-preview in the input field. This would allow users to:
Format code blocks using language.
Use other basic Markdown elements like lists (-, 1.), bold/italic, or inline code.

Implementation Ideas:
Simple Render-on-Send: The message input is parsed and converted to formatted HTML upon sending, just like the assistant's messages are.
Live Preview Pane: Add a small preview pane below the input field that shows how the message will look.
Formatting Toolbar: Introduce a simple toolbar above the input with buttons for code blocks (</>), bold, italic, etc., similar to GitHub comments or Stack Overflow.
A clear and concise description of any alternative solutions or features you've considered.

Originally created by @VAUsIGT on GitHub (Dec 16, 2025). Original GitHub issue: https://github.com/deepseek-ai/DeepSeek-V3/issues/1058 **Problem Statement:** Currently, users cannot format their messages using Markdown syntax (like code blocks with triple backticks) in the DeepSeek web chat. While the assistant's responses are beautifully rendered with proper code formatting and syntax highlighting, user input is displayed as plain text. This creates a disjointed and less productive experience, especially when discussing technical topics, sharing code snippets, or asking for debugging help. <img width="374" height="192" alt="Image" src="https://github.com/user-attachments/assets/fc8bc684-d42e-4706-b1b5-626784d12f63" /> **Alternatives that I have considered:** - Sending the code without formatting: This is the current "workaround", but it greatly reduces readability, especially for multi-line code. - Using external services: Creating snippets on third-party platforms (like GitHub Gist) and sending links. This disrupts the workflow and requires additional actions. **Proposed Solution:** Implement client-side Markdown rendering for user messages before they are sent or live-preview in the input field. This would allow users to: Format code blocks using language. Use other basic Markdown elements like lists (-, 1.), bold/italic, or inline code. **Implementation Ideas:** Simple Render-on-Send: The message input is parsed and converted to formatted HTML upon sending, just like the assistant's messages are. Live Preview Pane: Add a small preview pane below the input field that shows how the message will look. Formatting Toolbar: Introduce a simple toolbar above the input with buttons for code blocks (</>), bold, italic, etc., similar to GitHub comments or Stack Overflow. A clear and concise description of any alternative solutions or features you've considered.

bsakaguchi

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

closed this issue
added the
stale

closed-as-stale
labels

bsakaguchi commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Jan 16, 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 (Jan 16, 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:54 +00:00

Author

Owner

@github-actions[bot] commented on GitHub (Jan 30, 2026):

false

@github-actions[bot] commented on GitHub (Jan 30, 2026): false