Changelog / release
0.10.9 — share serve-flag passthrough + MTP K=3 default
Released 2026-07-12 · full changelog · GitHub releases
- Systematic serve-flag passthrough over
share.rapid-mlx share <model> -- <serve flags>now forwards everything after a literal--verbatim to therapid-mlx servethat share spawns (the git / cargo / kubectl end-of-options idiom), so every serve flag works over the tunnel without share re-declaring each one. A prefix-aware denylist keeps share-owned flags (--host/--api-key/--port/--listen-fd/--log-level) from being forwarded, preventing accidental LAN re-exposure or API-key override (PR #1096). - Spec-decode over share is opt-in, MTP K=3 by default. Speculative decoding stays off by default across a share; opt in per-share with
-- --force-spec-decode --speculative-config '{"method":"mtp"}'. When--force-spec-decodeis set, MTP defaults to K=3 unless you pass an explicitnum_speculative_tokens(--mtp-max-kand--speculative-configare mutually exclusive).