Key takeaways

  • DeepSeek's chat-demo is a static web app: no application backend, the browser talks straight to the API service.
  • Edit prompts, regenerate replies and switch between message branches without losing earlier answers.
  • Attach files, dictate by voice and have replies read aloud, in English or Simplified Chinese.
  • Chats stay in your browser's own storage, and exports leave out your API key.
  • The catches: you need your own API key, and your content is sent to the configured API service.

What it is

chat-demo is, in its own words, a static chat demo powered by the DeepSeek API. It is released under the MIT licence, and the code is on GitHub at deepseek-ai/chat-demo.

The problem it solves

Developers who want a polished chat interface for a model API usually have to build one, along with a server to sit in the middle. Here, no application backend is required: the browser connects directly to the configured API service, and you enter your own API key in Settings before the first chat.

What you get

  • Room to experiment: you can edit prompts, regenerate replies and switch between message branches.
  • Richer answers: streaming replies, deep thinking, smart search, link reading and source citations are listed among the features.
  • More than text: attach files by upload, paste or drag and drop, use voice input and have replies read aloud.
  • Local history: the API key and settings sit in the browser's localStorage, while conversations and original attachments are kept in IndexedDB.
  • Portable chats: exports include conversations and locally available original images, but leave out API keys and settings.

The catches

  • Privacy: sending messages, uploading attachments and using speech features sends the relevant content to the configured API service.
  • Deletion has limits: removing chats locally does not delete files already uploaded to the API service.
  • Your key lives in the browser: the API key is held in localStorage, so treat the device and browser profile accordingly.
  • Compatibility: the app sends extra request fields, so the configured service must support the corresponding capabilities.
  • Local file use: opening the built page directly depends on browser support and on an API service that permits cross-origin requests.

What we did not test

We did not run chat-demo, enter an API key, send a message or try the voice and attachment features. Every claim here comes from a literal quote in the project's README or the GitHub API, and the feature descriptions are the project's own. We also did not check how well it behaves on mobile or with other API services.

Verdict

Editors' view: this is most useful to developers who already use the DeepSeek API and want a ready-made chat front end, or a reference for building a browser-only client. Casual users will need to bring a key and accept that their content leaves the browser. If you try it, use a limited key and avoid sensitive material.

Repository
deepseek-ai/chat-demo
TypeScript · MIT
View on GitHub ↗

Sources

Need help adopting this, or have a software project in mind?

Tell us what you are building. The initial consultation is free. Email [email protected] or follow @zolnaltd.

Start a conversation →