DeepSeek chat-demo: a backend-free open chat front end for the official API
DeepSeek open-sourced chat-demo: a static chat front end that calls the API from the browser, with deep thinking, search citations, voice and MIT licensing.
Project facts
GitHub Ecosystem- License
- MIT
- Language
- TypeScript
- Stars
- 3,759
- Data checked
- 2026-11-16
Snapshot figures reflect the check date and may change over time.
Giving DeepSeek’s API a usable chat interface used to mean writing a front end yourself or adopting an open-source project that needs a server and a database. chat-demo goes the other way, and it is DeepSeek’s own: a static site with no application backend, where the browser talks directly to the configured API service. Drop the build output on any static host, or open dist/index.html directly. GitHub’s API reported 3,759 stars on November 16, 2026.
Core features
- Conversations and branches: chats are titled automatically and can be renamed or deleted; prompts can be edited, replies regenerated, and message branches switched. That matters when you compare candidate answers side by side.
- Deep thinking and web search: streaming replies, deep thinking, smart search, link reading and source citations; generation can be stopped at any time, and eligible replies can be continued.
- Attachments and voice: upload, paste or drag files into the chat, use voice input and read replies aloud; a live audio spectrum appears in the input area’s first row while recording.
- A complete renderer: Markdown, syntax highlighting, KaTeX math and Mermaid diagrams, plus Simplified Chinese and English, light and dark themes, mobile layouts, location settings, and chat history import/export.
- Data stays in the browser: the API key and settings live in localStorage, while conversations and original attachments live in IndexedDB, isolated per browser profile.
Typical use cases
- Fast API and prompt testing: no backend to deploy — start it locally and test DeepSeek’s models, search and citation behavior.
- A chat entry point for intranets or offline setups: the build is static files, so an internal static server is enough; there is no Node service or database to maintain.
- A reference implementation for your own product: the official demo shows conversation branching, citation display and voice interaction, a reasonable starting point for a custom chat front end; for constrained generative UI rendering, compare OpenUI.
Quick start
The README’s flow needs Node.js 22.12+ and pnpm:
git clone https://github.com/deepseek-ai/chat-demo.git
cd chat-demo
pnpm install
pnpm dev
Then open http://localhost:8090. Build the static site with pnpm build; the output lands in dist/ for any static server. Opening dist/index.html directly requires browser support for the relevant local storage APIs. You can also try the online demo first.
Summary
chat-demo’s value is delivering official capability with minimal engineering: no backend, no database, MIT licensed, browser-to-API. Its limits are equally clear — data lives in browser storage, so switching devices or clearing the cache loses it, and the API key sits in localStorage, which deserves care on shared machines. GitHub’s API reported TypeScript, MIT, 3,759 stars, an unarchived repository and a last push on November 13, 2026, on November 16, 2026.
The engineering boundary is worth noting too: pure static means all logic runs on the client, so a leaked API key cannot be revoked server-side — put your own proxy or short-lived credentials in front before shipping it internally. Conversations live in IndexedDB, and browser cleanup policies can clear them at any time, so export anything important. Compared with open-source chat projects that need a server and database, it drives deployment cost to near zero and, with it, hands data governance to the user.
This entry is based on the README and the online demo; we did not deploy it locally. Actual behavior and model availability depend on the API service you configure.