deepseek-ai/chat-demo

This page introduces an external open-source repository. It is not an HDATF product.

What it does

chat-demo is a static DeepSeek chat interface for users and developers who want an API client without an application backend. Users provide an API key, prompts, attachments, or voice input and receive streaming replies with supported reasoning, search citations, and rendered Markdown, mathematics, or diagrams. The browser calls the configured API directly, using Anthropic-compatible Messages and Files interfaces and separate speech endpoints. Conversation branches support prompt editing, regeneration, and switching between alternative replies. API keys and settings stay in localStorage, while conversations and original attachments are stored in IndexedDB, but submitted content is sent to the API service. A release archive can be opened through its index.html, while source development uses Node.js 22.12 or newer, pnpm, React, TypeScript, and Rspack. The default origin is api.deepseek.com and the documented default model is deepseek-flash, so another service must support the same extensions and cross-origin requests. ZIP history import replaces local history after validation, exports omit original non-image attachments, and deleting local chats does not remove files already uploaded to the service.

License

MIT Permissive. Commercial use and changes are allowed if the copyright notice is kept.

More in this category

• vercel-labs/ui
  UI SDK is a UI library for developers and coding agents to reuse interaction behaviors. It is not a finished business app or model, but a toolkit for keyboard navigation, focus, selection, popups and accessibility attributes. Developers define state, actions and component parts, then render actual elements through a framework adapter. It supplies a shared core and adapters for React, Vue, Svelte, Solid and Web Components. The official example connects a search input and clear button to one behavior definition. The dialog source also separates state, slots and actions exposed to agents. Getting started requires connecting core and the appropriate framework package to an app; the agent skill is a separate addition. Installing packages does not automatically convert existing screens. The product is beta, so APIs and behavior may change and accessibility still needs testing in the actual interface.
• expo/exact
  Exact is an application runtime for developers who want one interface definition to serve web, macOS, iOS and Linux apps. Its inputs are Contract, a declarative language for views, state and actions, plus TypeScript or Rust data logic. The compiler produces a plan that becomes browser DOM and CSS on the web, while a Rust runner and layout kernel drive native controls or painting on other hosts. Data reads and writes cross a typed boundary, and declared grants restrict access to networking, files, SQLite and secrets. An agent driver exposes tree inspection, screenshots, interaction, state and clock control through a shared interface, with Contract tests reusable across hosts. The repository includes todo and local notebook examples rather than an already configured business application. Setup depends on a source checkout, Rust, pinned Bun and Chrome, with Xcode required for Apple targets and a pinned Hermes JavaScript runtime for native TypeScript. This is a changing pre-1.0 project without compatibility guarantees, while Windows control parity and delivery, Android packaging and Linux editing remain incomplete.
• anomalyco/rune
  Rune is a UI framework that builds interfaces from Rust code and renders them on the GPU. Its main documentation targets macOS, Windows, Linux and the web and covers interface inspection by coding agents as well as people. Inputs are application state, view functions and human or scripted interactions; outputs are running interfaces or headless PNGs and element trees. The inspected hello example changes state when a switch is clicked and updates its text and knob position accordingly. Its test uses virtual pointer input and frame advancement to check the state change and knob movement. Core documentation describes layout, text, theme tokens, spring animation and headless input. Adoption requires connecting Rune as a Rust project dependency and writing state and views; installation does not convert an existing application. It is pre-release, so the documentation recommends pinning a specific dev revision, and target-platform graphics, real input and accessibility support require separate validation before adoption.
• meta/astryx
  Astryx is a design system that supplies React components together with visual conventions. It is intended to give developers, designers and coding agents a shared component reference. Inputs are React code, component properties and theme settings, and outputs are web interfaces such as buttons, forms and page layouts. It supplies prebuilt CSS and typed React components, with CSS custom properties controlling theme appearance. Its CLI can retrieve component documentation, emit page template source and eject component source into a project for customization. Adoption requires React 19 or later and the relevant packages, ordered stylesheet imports and a connected theme provider. Ordinary consumption needs no separate StyleX build plugin, but installing packages does not automatically convert existing screens or configure an agent. The project is in beta, and experimental components and some chart packages are outside stable distribution, so package release status needs separate checking.
• ppmpreetham/BUI
  BUI is a library for developers building standalone desktop interfaces with Blender-like widgets without installing Blender. It accepts interface code and input events, then produces windows or offscreen pixel buffers and interaction callbacks. Bindings include Python, Rust, JavaScript, React, Svelte, C, C++ and Dear ImGui, with syntax layers for tkinter and parts of Qt. The common execution layer is a retained-node C runtime that reimplements interface drawing and interaction rather than running Blender's full application. Software rasterization is the default, with optional Direct3D 11 rendering on Windows and OpenGL 3.3 on Linux. Environment requirements depend on the binding, and macOS support is experimental with additional restrictions. Compatibility syntax is not complete behavioral equivalence, and the documentation lists missing accessibility APIs, input-method support and per-character font fallback. The project declares GPL-3.0-or-later, and its promotional speed comparisons do not establish performance in a particular application.

Only repositories in the ranked Trendshift lists are included, and the lists are used only to find candidates. We do not copy their ranks. Descriptions, licenses and star counts come from each GitHub repository. The notes are our own reading. We have not tested these projects, and a place on a trending list does not prove quality.