local-llmlisted

# Local LLM Setup (LM Studio + mlx-dspark) ## Announce at start "I'm using the local-llm skill to work with the local inference setup." ## Architecture Two local LLM backends exist on this machine, serving the same underlying model family (`Qwen3.8-27B`, 4-bit, hybrid attention -- see RAM cheatsheet below): | Backend | Port | Role | Managed by | |---|---|---|---| | **LM Studio** | 1234 | Interactive chat UI use only | LM Studio app itself (own TTL-based auto-unload) | | **mlx-dspark** | 8090 | Production -- everything `build_local.py` and any script under `systems/superintelligence/*` talks to | `launchd` (`~/Library/LaunchAgents/com.local.mlx-dspark.plist`) | `build_local.py` (all 6 copies under `systems/superintelligence/{data-analytics, finance,gtm,risk-compliance,strategy,trading}/scripts/`) talks **only** to mlx-dspark. LM Studio is not in that pipeline's path at all -- it exists purely for manual/interactive use. Do not assume both are always loaded; see "Idle-unload" below. Config lives outside the repo (never committed, never touched by git): - `~/.config/mlx-dspark/start.sh` -- the server launch command (model, mode, context window, batch size, host/port, API key). - `~/.config/mlx-dspark/api_key` -- 0600-perms API key file. `build_local.py` reads `MLX_DSPARK_API_KEY` env var first, falls back to this file. - `~/.config/mlx-dspark/idle_watcher.py` -- the idle-unload poller (see below). - `~/Library/LaunchAgents/com.local.mlx-dspark.plist` -- the server's La