AI News

DeepSeek open-sources the chat-demo frontend, integrating the same search, link reading, and voice features as the App

Shao MengUpdated Nov 16 21:11

AI summary

DeepSeek announced in its official API documentation that it is opening up the App's capabilities—including web search, file parsing, link reading, safety moderation, and voice—as APIs, and has open-sourced the reference frontend chat-demo, which surpassed 3,000 stars within three days of release. The demo has no application backend; the browser sends requests directly to the API. The default model is hardcoded as deepseek-flash, chat goes through the Anthropic-compatible Messages / Files interfaces, and voice goes through separate ASR and TTS. Search and link reading are handled server-side, all generation requests are fixed to include safety_check: high, the API Key is stored in localStorage, and conversations and attachments are stored in IndexedDB.

Why read this

AI score 62

The original article breaks down how chat-demo uses a static frontend to replicate the App's search, link reading, and voice pipelines, and examines the design trade-offs of the server-side tools and callback protocol.

Topics

Tags

Body · AI translation

DeepSeek open-sources chat-demo: use a static frontend to connect to the App's search, link reading, and voice features

On 11.13, DeepSeek announced in its official API documentation that it is opening up the App's capabilities such as web search, file parsing, link reading, safety review, and voice to developers in the form of APIs, and at the same time open-sourcing the reference frontend chat-demo. Three days after open-sourcing, it already has over 3,000 Stars!

Open-source address: https://t.co/EI6WyzAxhy Online experience: https://t.co/6BBnsOntJQ

# A reference client with no application backend

The browser directly requests the configured API, which by default is https://t.co/3FwgW6PKlb. You can try it online, or download the zip package from Releases and double-click index.html; local development requires Node.js 22.12+ and pnpm. When opening directly as a local file, both the browser and the API must allow file:// storage and cross-origin requests.

The default model is hardcoded in the code as deepseek-flash. Chat goes through the Anthropic-compatible Messages / Files interfaces, and voice goes through separate ASR and TTS. Multi-session, message branching, streaming answers, deep thinking, search citations, attachments, and read-aloud are all designed to match the official App experience.

# Search and link reading are completed on the server side

The client is responsible for displaying the returned content blocks and, in the next round, sending back the parts that should be returned exactly as they are. The link reading tool is always declared; whether to add deepseek_web_search is determined by the local smart search toggle; deep thinking corresponds to thinking. All generation requests are fixed to carry safety_check: high, so they go through the protocol with server-side tools. The system prompt is a fixed identity statement: "This assistant is DeepSeek, created by DeepSeek Company."

When sending back, historical thinking and search results are no longer sent; only links that were successfully read carry a signature, for the server to restore the webpage body text. If the server gives a safety refusal, the thinking and body text that have already streamed down must be discarded by the client, keeping only the tool blocks. If a new conversation does not yet have a title, at the end it will request an automatic title from the server. Each round also inserts latest_reminder, whose content is the date, day of the week, location, Web, and interface language, with the date calculated according to the browser's local time zone.

The API Key and settings are stored in localStorage, and conversations and original attachment files are stored in IndexedDB. Sending, uploading, and voice all pass the corresponding content to the API; clearing the local conversation will not delete files that have already been uploaded to the server. History import and export use ZIP, the format version is export_format_version: 3, and records exported by the official DeepSeek can be imported; importing will replace all local conversations. Export does not include the API Key or original non-image attachment files, and imported replies cannot continue to be generated.

Source

Shao Meng