rapid-mlx-dsh-provider

@raullenchai/dsh-provider

A native Rapid-MLX provider for DeepSeek Harness — so dsh gets its model facts from the server instead of from whatever you typed into settings.yaml. Status: published to npm as @raullenchai/dsh-provider. The end-to-end dsh run in Verified was on an M3 Ultra against dsh 0.1.0-rc.7; dsh 0.1.0-rc.8 is API-compatible — the LlmAdapter contract is byte-identical and the only changes are additive — and the adapter is re-verified against rc.8 at the protocol and unit-test level. DSH is still a developer preview that moves fast, so treat this as tracking a moving target, not a frozen compatibility promise. What it does for you

DSH can already talk to a local Rapid-MLX server through its generic openai-completions provider. That route works — but it knows nothing about your model beyond what you hand-wrote:

Rapid-MLX's /v1/models already publishes all of that and more. This adapter reads it, so:

1. Nothing to hand-write, and nothing to re-write when you switch models. Swap what rapid-mlx serve is running and dsh follows. No re-running setup, no stale numbers.

2. The reasoning control tells the truth. Rapid-MLX reports whether a model actually has a reasoning parser. A model that can't reason no longer shows an off/low/medium/high selector that does nothing.

3. Compaction is timed with the capacity that actually fits this Mac, not a number that drifted. This is the one that quietly costs you. dsh-compaction-basic asks the provider for the route's capacity and compacts at thresholdRatio × capacity (0.8 by default). The provider prefers the server's max_model_len — Rapid-MLX's memory-fitted ceiling (what fits in unified memory: weights + KV cache), in the vLLM/SGLang-standard field — over the native context_window, and falls back to context_window on an older server that doesn't report it. So compaction is timed to what the machine can actually hold, not the model's advertised window (which it may not have room for) and not a hand-written number copied from another model. Install

Needs Node ≥ 22.15 (dsh imports Node's Zstd stream API without declaring it) and a running Rapid-MLX server.

Then point the agent at the route:

Verified: that command installs and activates as a profile layer against dsh 0.1.0-rc.7. To hack on it locally instead, see Local development. Model management (v0.2.0)

Beyond the provider route, the plugin registers five tools and a /rapid-mlx command so the agent can see and manage models without leaving the session. The split follows which surface actually owns each fact: served-model facts come from the structured HTTP /v1/models; the download cache and pull/remove are CLI-only, so those — and only those — shell out to rapid-mlx through the harness subprocess seam. /rapid-mlx prints a one-shot overview: health, the served model and its facts, and total cache disk usage.