HN reacted because this was less about one wrapper and more about who gets credit and control in the local LLM stack. The Sleeping Robots post argues that Ollama won mindshare on top of llama.cpp while weakening trust through attribution, packaging, cloud routing, and model storage choices, while commenters pushed back that its UX still solved a real problem.
Reddit lit up around a build that turns a Xiaomi 12 Pro into a headless Gemma 4 server because it feels much closer to how most people actually tinker with local AI. The excitement was not about peak numbers, it was about proving that useful local inference can live on everyday hardware.
LocalLLaMA upvoted this because it pushes against the endless ‘48GB build’ arms race with something more practical and more fun: repurposing a phone as a local LLM box. The post describes a Xiaomi 12 Pro running LineageOS, headless networking, thermal automation, battery protection, and Gemma4 served through Ollama on a home LAN.
Daniel Vaughan’s Gemma 4 writeup tests whether a local model can function as a real Codex CLI agent, with the answer depending less on benchmark claims than on very specific serving choices. The key lesson is that Apple Silicon required llama.cpp plus `--jinja`, KV-cache quantization, and `web_search = "disabled"`, while a GB10 box worked through Ollama 0.20.5.
A practical HN gist lays out how to run Ollama and Gemma 4 on an Apple Silicon Mac mini, including auto-start, periodic preload, and `OLLAMA_KEEP_ALIVE=-1`. The author says `gemma4:26b` nearly exhausted 24GB unified memory, making the default 8B model a safer operational choice.
A March 31, 2026 Hacker News hit brought attention to Ollama’s new MLX-based Apple Silicon runtime. The announcement combines MLX, NVFP4, and upgraded cache behavior to make local coding-agent workloads on macOS more practical.
Ollama used a March 30, 2026 preview to move its Apple Silicon path onto MLX. The release pairs higher prefill and decode throughput with NVFP4 support and cache changes aimed at coding and agent workflows.
Ollama said on March 26, 2026 that VS Code now integrates with Ollama via GitHub Copilot. Ollama docs say VS Code 1.113+, GitHub Copilot Chat 0.41.0+, and Ollama v0.18.3+ let users load local or cloud Ollama models into the Copilot model picker, with GitHub Copilot Free sufficient for custom model selection.
A detailed engineering write-up resonated on Hacker News because it treated production RAG as a data and operations problem, not a prompt demo.
Ollama said on March 18, 2026 that MiniMax-M2.7 was available through its cloud path and could be launched from Claude Code and OpenClaw. The Ollama library page describes the M2-series model as a coding- and productivity-focused system with strong results on SWE-Pro, VIBE-Pro, Terminal Bench 2, GDPval-AA, and Toolathon.
Ollama said on March 20, 2026 that NVIDIA’s Nemotron-Cascade-2 can now run through its local model stack. The official model page positions it as an open 30B MoE model with 3B activated parameters, thinking and instruct modes, and built-in paths into agent tools such as OpenClaw, Codex, and Claude.
A high-scoring LocalLLaMA post says Qwen 3.5 9B on a 16GB M1 Pro handled memory recall and basic tool calling well enough for real agent work, even though creative reasoning still trailed frontier models.