The engine that quietly powers most of the local AI world just grew up. llama.cpp — the C/C++ inference library behind Ollama, LM Studio, and a long tail of apps that run models on ordinary hardware — released version 1.0.0 on Thursday, trading three and a half years of commit-number builds for semantic versioning and a promise: the public API is now stable, and breaking changes will arrive with a major-version bump.

The release landed on Thursday morning, announced on Hugging Face's blog and on r/LocalLLaMA by Merve, a Hugging Face engineer on the project, where it quickly became the subreddit's fastest-moving post of the day. The blog post frames v1.0 as a responsibility statement as much as a release: with more downstream apps depending on llama.cpp's library interfaces every year, the team is committing to make API and ABI breaks visible through major-version bumps — and to be stricter about them as adoption grows.

What 1.0 actually changes#

The headline change is a pruning. Version 1.0 removes the deprecated public API — 35 deprecated functions, plus the warmup setter and the defragmentation threshold option — and promotes the NextN speculative-decoding API into the main llama.h header. The message to developers is blunt: if your app was leaning on a deprecated call, it is time to move. The companion tensor library ggml ships as v1.0.0 at the same time, with its own deprecated API and legacy operations pruned.

Just as important is what does not change. The project has used raw commit numbers as version strings since its start in March 2023 — builds like '12360' that told you nothing about compatibility. From here on, llama.cpp follows semantic versioning: major bumps for breaking C API changes, minor for backward-compatible features and new model support, patch for bug fixes.

What's new under the hood#

Beyond the API work, v1.0 is a large feature release. It adds OCP FP8 key-value caches, a host-memory cache for mixture-of-experts models with a configurable CPU share, and loading of external PLE shards from separate GGUF files. Three new text architectures arrive — Kimi-K3.1-Pro, the 65-billion-parameter Ripple preview, and xing4_0 — alongside drama-3 text-to-speech and vision support for MageVL-Cowork and Kimi-K3.1. The project now supports more than 150 architecture variants.

llama-server, the OpenAI-compatible API server many apps talk to, gets a security pass: fixes for server-side request forgery via the CORS proxy, DNS rebinding, and child-instance access, plus an opt-in model for unauthenticated tools. It also gains a /v1/audio/speech endpoint, cancellation of MCP tool calls when a client disconnects, and a redesigned web UI with chat groups and a live-preview markdown editor.

A laptop running a local AI model on a desk at night, with a small llama figurine beside it
AI-generated illustration: local inference on a laptop, the setup llama.cpp is built for.

Distribution widens, too. Pre-release artifacts cover Linux, macOS, Windows, Android, and iOS, with Docker, Debian, Homebrew, conda-forge, MacPorts, Winget, and XCFramework channels listed in the release notes.

The desktop apps arrive with it#

The team used the announcement to flag a second product: Llama desktop apps for macOS and Windows, built on llama.cpp and aimed at making local AI a few clicks away rather than a build-from-source exercise. The apps are the project's most direct pitch to non-developers — the same engine, without the terminal.

The community's first reaction#

The announcement thread's most popular response was not a congratulation but a request: more maintainers. Readers pointed to a long backlog of open issues and pull requests, and argued that llama.cpp trails faster forks — naming Strata and unmerged performance work such as Adaptive KV — while Nvidia's Dory model support, proposed in pull request #30306, still waits to be merged. Others pushed back, noting that llama.cpp still runs on legacy hardware the forks have dropped. Nobody in the thread disputed the release itself; the argument is about pace, not about whether 1.0 is real. With more than 134,000 GitHub stars, the project is one of the most watched open-source AI repositories in the world — and the maintenance question is now attached to a stable API promise.

A desktop PC, laptop, phone and single-board computer connected by glowing lines, with a llama silhouette behind them
AI-generated illustration: one engine across every device, from servers to phones.

What to watch#

For anyone building on llama.cpp, the immediate job is migration: audit for removed API calls before upgrading, and expect the stricter versioning to make future breaks easier to plan around. The longer question is whether the stability promise comes with the maintainer capacity to keep it. A 1.0 release is a foundation, not a finish line — and the community's first ask was not for more features, but for more hands.

Sources: Hugging Face — llama.cpp v1.0.0: A stronger foundation for the local AI ecosystem (Nov. 13, 2026); GitHub — Release v1.0.0, ggml-org/llama.cpp (Nov. 13, 2026); r/LocalLLaMA — llama.cpp v1.0 is here (Nov. 13, 2026, 9:07 a.m. ET). Cover image: llama.cpp brand cover, ggml-org/llama-brand (MIT).