# ds4 (DwarfStar) — user guide A from-source build of [`antirez/ds4`](https://github.com/antirez/ds4), a local inference engine for **DeepSeek V4 Flash/PRO**. This is a short operational guide; see the [upstream README](https://github.com/antirez/ds4) for the full documentation (server API, agent, distributed inference, tuning, etc.). ## What's installed The package builds for a chosen GPU backend (`cpu`, `rocm`, or `cuda`) and installs these binaries: | Binary | What it does | |---|---| | `ds4` | Interactive CLI chat / one-shot `-p "..."` | | `ds4-server` | OpenAI/Anthropic/Responses-compatible HTTP API | | `ds4-agent` | Native terminal coding agent (alpha) | | `ds4-bench` | Throughput benchmarking | | `ds4-eval` | Capability/regression eval harness | | `ds4-download-model` | Helper to fetch GGUF weights (see below) | There is **no graphical UI**. `ds4-server` exposes a URL you can point an OpenAI-compatible client at. ## 1. Get the weights Weights are **not** packaged. They live at the project's Hugging Face repo [`antirez/deepseek-v4-gguf`](https://huggingface.co/antirez/deepseek-v4-gguf) (public, MIT, no token needed) and only these custom GGUFs work — not arbitrary DeepSeek GGUFs. `ds4-download-model` writes into `./gguf` and links `./ds4flash.gguf` in the current directory (override the root with `DS4_HOME`, or the gguf dir with `DS4_GGUF_DIR`): ```sh ds4-download-model q2-imatrix # ~81 GB, the pick for 96/128 GB machines ds4-download-model --help # all targets (q4-imatrix, pro-*, mtp, ...) ``` Pick by machine memory: `q2-imatrix` (128 GB), `q4-imatrix` (≥256 GB), `pro-*` (512 GB / distributed). The small/Flash quants download via `curl`; the huge **PRO** files need the `hf` CLI (not bundled — `nix shell nixpkgs#huggingface-hub`). ## 2. Run it ```sh # interactive chat (defaults to ./ds4flash.gguf in the current dir) ds4 # explicit model path ds4 -m /path/to/gguf/DeepSeek-V4-Flash-IQ2XXS-...-imatrix.gguf # HTTP server on the LAN ds4-server -m ./ds4flash.gguf \ --ctx 100000 --kv-disk-dir ./kv --kv-disk-space-mb 8192 --host 0.0.0.0 ``` Then point a client at `http://:8000/v1` (endpoints: `/v1/chat/completions`, `/v1/messages`, `/v1/responses`, ...). Use `--cors` for browser clients. ## Backend notes - **rocm** targets a specific GPU arch (default `gfx1151`, AMD Strix Halo). At runtime the user needs `/dev/kfd` + render-node access, and large models need the GTT memory kernel params from upstream's `STRIXHALO.md`. On Strix Halo, export `HSA_ENABLE_SDMA=0` (SDMA is buggy on its unified memory). - **cuda** is unfree (CUDA closure) and needs an NVIDIA driver at runtime. - **cpu** is a reference/debug path only — not for production inference. ## Maintenance This tracks upstream `main` (no releases). To bump, set `rev` in `default.nix` and refresh `hash`. Binaries are built per-host (`-march=native`), so build each GPU variant on its target host. See `default.nix`'s header comment for details.