LlamaStation v0.9 — llama.cpp GUI for Windows with multi-backend support, TurboQuant, MTP and more
Mirrored from r/LocalLLaMA for archival readability. Support the source by reading on the original site.
I've been building this for the past few months as a side project — started because I didn't want to run llama.cpp from the command line every time I wanted to try a model. I just wanted something that worked with a click.
Fair warning: I'm not a developer. This is 100% vibe coded with AI assistance. If something in the codebase makes you cringe, please be kind and open a PR instead 🙏
Most frontends either hide everything behind abstractions (Ollama, LM Studio) or leave you writing command lines manually. LlamaStation tries to sit in the middle: a clean UI with full access to every parameter.
What makes it different
Runs llama-server directly — no intermediate layer, no daemon, no abstraction. LlamaStation launches llama-server.exe as a subprocess with full control over every flag. What you configure is exactly what gets passed to the binary. This means you get the full performance of llama.cpp with none of the overhead that tools like Ollama add on top.
Multiple backends, switchable from the UI:
⚡ Official llama.cpp (with MTP support since PR #22673)
🔬 TurboQuant fork — asymmetric KV cache quantization. This is the killer feature for me: 200k+ context on 24GB VRAM (dual RTX 3060) with minimal quality loss
⚛️ AtomicChat — TurboQuant + MTP combined
🐝 BeeLlama — DFlash + TurboQuant (experimental)
Real-time VRAM meter per GPU — color coded, updates live as the model loads.
Per-model profiles — every setting remembered automatically per model file.
Voice mode — push-to-talk or always-listening, voice cloning via XTTS v2, speech recognition via faster-whisper. Fully offline.
Headless mode — run without GUI using saved profiles, for servers or automation.
Auto-updater — updates llama.cpp official (and checks AtomicChat releases) from inside the app.
My setup for context
Dual RTX 3060 (24GB total), Ryzen 7 5700X, 32GB DDR4 3600MHz, Windows 11. Running Qwen3.6 27B Q4_K_M with TurboQuant KV cache and MTP — 177k context. Without MTP the same model starts at ~17 tok/s and drops to ~10 on long responses. With MTP it starts at ~29 tok/s and holds at ~22 even on long code generation. This is what I built LlamaStation for.
Status
v0.9 — it works well for my daily use. I've fully replaced other tools with it — I use it as the backend for coding agents, Telegram bots, voice assistants and other local automations. There's one known bug (server watchdog gets stuck in "restarting" state after OOM crash) and probably others I haven't hit yet. Opening it up to get feedback and contributions.
Not a programmer by trade — built this entirely with AI assistance. The codebase is a single main file by design, easy to read and modify.
Contributions very welcome — especially:
Linux/Mac port (currently Windows only)
Bug fixes
New backend integrations
UI improvements
GitHub — MIT license, no telemetry, no accounts.
[link] [comments]
More from r/LocalLLaMA
-
How small can the orchestration model in an agent be? (separating it from code-gen — that obviously wants a big model)
May 22
-
BeeLlama v0.2.0 – major DFlash update. Single RTX 3090: Qwen 3.6 27B up to 164 tps (4.40x), Gemma 4 31B up to 177.8 tps (4.93x). Prompt processing speed near baseline.
May 22
-
trained a prompt injection detector using ml-intern and DeepSeek v4 Flash, runs in the browser
May 22
-
ByteShape Qwen3.6-35B-A3B: 30% faster than Unsloth IQ on 6GB VRAM laptop
May 22
Discussion (0)
Sign in to join the discussion. Free account, 30 seconds — email code or GitHub.
Sign in →No comments yet. Sign in and be the first to say something.