deepseek-ai/DeepSeek-V3

Fork 0

mirror of https://github.com/deepseek-ai/DeepSeek-V3.git synced 2026-11-05 00:47:48 +00:00

[GH-ISSUE #1014] [feature request] support for text only browsers #623

New issue

Closed

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

bsakaguchi commented

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

Owner

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

With chat deepseek being a text centered interface it is somewhat strange that a text only browser is unnable to interact with it.
It would be awsome if it was possible to use something like emacs eww to chat with deepseek, but eww does not support javascript.
Is there something you could do for a javacriptless client?

Originally created by @RedJocker on GitHub (Oct 16, 2025). Original GitHub issue: https://github.com/deepseek-ai/DeepSeek-V3/issues/1014 With chat deepseek being a text centered interface it is somewhat strange that a text only browser is unnable to interact with it. It would be awsome if it was possible to use something like emacs eww to chat with deepseek, but eww does not support javascript. Is there something you could do for a javacriptless client?

bsakaguchi

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

closed this issue
added the
stale

closed-as-stale
labels

bsakaguchi commented

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

Author

Owner

@Abhinavvel2006 commented on GitHub (Oct 18, 2025):

Hi @RedJocker, thanks for raising this thoughtful feature request!

You're absolutely right — DeepSeek's chat interface being text-centric makes it a natural fit for text-only environments, and it's unfortunate that JavaScript dependency blocks access via browsers like Emacs EWW.

Here are a few ideas we’re exploring to make DeepSeek more accessible:

Minimal HTML-only interface: A lightweight, JavaScript-free version of the chat UI using plain HTML forms and server-side rendering
Command-line client: A CLI tool (Python or Node.js) that interacts with DeepSeek via API. This would allow users to chat from terminal-based environments like Emacs, Vim, or shell.
Public API access: If not already available, exposing a simple RESTful API would empower users to build their own integrations for text-only workflows.

@Abhinavvel2006 commented on GitHub (Oct 18, 2025): Hi @RedJocker, thanks for raising this thoughtful feature request! You're absolutely right — DeepSeek's chat interface being text-centric makes it a natural fit for text-only environments, and it's unfortunate that JavaScript dependency blocks access via browsers like Emacs EWW. Here are a few ideas we’re exploring to make DeepSeek more accessible: 1. Minimal HTML-only interface: A lightweight, JavaScript-free version of the chat UI using plain HTML forms and server-side rendering 2. Command-line client: A CLI tool (Python or Node.js) that interacts with DeepSeek via API. This would allow users to chat from terminal-based environments like Emacs, Vim, or shell. 3. Public API access: If not already available, exposing a simple RESTful API would empower users to build their own integrations for text-only workflows.

bsakaguchi commented

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

Author

Owner

@RedJocker commented on GitHub (Oct 18, 2025):

hey thank for the response, it is nice to see that the idea is appretiated and an implementation is being considered.

I like all 3 ideas, number 1 is more to the spirit for general text only browsers, so a lynx user could also interface with chat deepseek.
but for an emacs user any of 3 proposed would be fine, it is just so easy to make wrappers to run shell commands and to make tcp connections that any of these would work to improve the experience. Very likely someone would end up including this in a package to make even easier.

@RedJocker commented on GitHub (Oct 18, 2025): hey thank for the response, it is nice to see that the idea is appretiated and an implementation is being considered. I like all 3 ideas, number 1 is more to the spirit for general text only browsers, so a lynx user could also interface with chat deepseek. but for an emacs user any of 3 proposed would be fine, it is just so easy to make wrappers to run shell commands and to make tcp connections that any of these would work to improve the experience. Very likely someone would end up including this in a package to make even easier.

bsakaguchi commented

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

Author

Owner

@Abhinavvel2006 commented on GitHub (Oct 19, 2025):

Thanks @RedJocker — really appreciate your thoughtful follow-up!

I agree, idea #1 feels most aligned with the spirit of text-only browsers like Lynx. I’ve started prototyping a minimal HTML-only interface using Flask — no JavaScript, just plain form submission and server-rendered responses. It’s already working in Emacs EWW and should be compatible with Lynx too.

For Emacs users, I love the idea of wrappers or TCP-based integrations. Once the basic interface is stable, I’ll explore exposing a simple REST API so folks can build their own clients or packages around it. Your point about shell command wrappers is spot-on — Emacs users are incredibly resourceful, and I’d love to support that flexibility.

I’ll share a link or repo soon once it’s ready for testing. Thanks again for sparking this — accessibility and inclusivity are goals I care deeply about, and this is a great direction to push forward.

@Abhinavvel2006 commented on GitHub (Oct 19, 2025): Thanks @RedJocker — really appreciate your thoughtful follow-up! I agree, idea #1 feels most aligned with the spirit of text-only browsers like Lynx. I’ve started prototyping a minimal HTML-only interface using Flask — no JavaScript, just plain form submission and server-rendered responses. It’s already working in Emacs EWW and should be compatible with Lynx too. For Emacs users, I love the idea of wrappers or TCP-based integrations. Once the basic interface is stable, I’ll explore exposing a simple REST API so folks can build their own clients or packages around it. Your point about shell command wrappers is spot-on — Emacs users are incredibly resourceful, and I’d love to support that flexibility. I’ll share a link or repo soon once it’s ready for testing. Thanks again for sparking this — accessibility and inclusivity are goals I care deeply about, and this is a great direction to push forward.

bsakaguchi commented

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

Author

Owner

@RedJocker commented on GitHub (Nov 7, 2025):

Hi I'm very happy to see this moving forward!
I'll certainlly be glad to help testing, I can even try to recruit more people to test the feature

@RedJocker commented on GitHub (Nov 7, 2025): Hi I'm very happy to see this moving forward! I'll certainlly be glad to help testing, I can even try to recruit more people to test the feature

bsakaguchi commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Dec 7, 2025):

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 (Dec 7, 2025): 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:14 +00:00

Author

Owner

@github-actions[bot] commented on GitHub (Dec 21, 2025):

false

@github-actions[bot] commented on GitHub (Dec 21, 2025): false