rigma 0.7.0

Hardware-aware local LLM deployment: probe, resolve, run.

Rigma

Hardware-aware local LLM deployment for consumer machines: rigma up probes your GPU/RAM, picks the community-verified best model + quant + flag combo for your exact hardware, downloads a pinned llama.cpp build and the model, and serves an OpenAI-compatible endpoint — no knob-mashing required.

Unlike generic runners, Rigma applies the tuning that actually matters per machine: MoE expert offload (--n-cpu-moe) sized to your RAM, architecture-aware KV-cache policies (e.g. q8_0 K-cache floor on DeltaNet-family models), backend selection per GPU generation (e.g. Vulkan over ROCm on RDNA4), flash attention, and session persistence (--slot-save-path) on by default. Every decision is auditable: rigma plan --explain shows the arithmetic and sources.

Quickstart (pre-alpha)

pip install rigma
rigma up            # probes your machine, downloads the best model, opens the chat UI

That's it — a browser tab opens with a chat connected to your tuned local model, and any OpenAI-compatible tool can use http://127.0.0.1:11500/v1.

Chats persist server-side across restarts — the browser UI lists past sessions in a rail, renders markdown (fenced code, copy button), and supports regenerate / edit-last. Each session carries its own system prompt (registry ships sensible defaults per use case — general, creative, coding — so creative-writing models stay in character from the first message) and a per-session "use my documents" RAG toggle with inline citations.

Commands

Command	What it does
rigma up	Start everything; opens the chat UI in your browser
rigma chat	Chat with the running model in the terminal; --session <id> resumes a session started in the browser UI
rigma status	What's running, where
rigma stop	Stop the model server and UI
rigma models	What fits your machine
rigma plan --explain	What up would run, with the math
rigma doctor	What Rigma detects on this machine
rigma update	Pull the latest community combo registry
rigma bench	Measure real speed; --evidence FILE exports registry-format proof
rigma rag add PATH	Index a folder into your local knowledge base (Raggity sidecar)
rigma rag ask "..."	Answer grounded in your documents, with citations, via your tuned model

rigma up flags: --use-case coding · --model SLUG · --port 11500 · --no-browser · --turbo (fast download, may hog your bandwidth) · --yes · --dry-run

Status

Pre-alpha (M5). rigma bench records machine-local calibration that outranks registry combos on your machine, and a failed launch automatically falls back (smaller quant → CPU floor) with each step explained. Combos come in two grades: verified (benchmarked on real hardware, evidence attached) and provisional (research-seeded fit math — run one and PR your numbers to rigma-registry). Verified so far:

Hardware	Model	Backend	Result
RX 9070 XT 16GB + 16GB RAM (Windows)	Qwen3.6-35B-A3B UD-Q3_K_XL, ctx 32K, n_cpu_moe 10	Vulkan (llama.cpp b9867)	verified 2026-07-06: 57.1 t/s gen, 689 t/s prefill @ 4K prompt

RAG (chat with your documents)

Rigma pairs with Raggity (AGPL-3.0, runs as a separate low-RAM process — ~300 MB) for grounded, cited answers from your own files through your tuned local model: pip install raggity[server], then rigma rag add <folder> and rigma rag ask "...". If raggity isn't on PATH, point RIGMA_RAGGITY_CMD at it.

Design: docs/superpowers/specs/2026-07-03-rigma-design.md. License: Apache-2.0.