llama.cpp reaches 1.0, making compatibility a first-class promise for local AI
llama.cpp reaches 1.0, making compatibility a first-class promise for local AI
The most important change in llama.cpp 1.0 is not another benchmark. It is a clearer contract for the developers building local-AI applications on top of it.
The maintainers released version 1.0.0 of both llama.cpp and its ggml tensor library on November 13. They say incompatible API and ABI changes will now trigger major-version increases. Their versioning table assigns backward-compatible functionality to minor releases and fixes without API changes to patches. The announcement explicitly frames this around downstream applications depending on library interfaces. Official announcement
That does not mean upgrading is consequence-free. This release removes 35 deprecated functions and other retired interfaces, while moving the NextN speculative-decoding API into the main public header. Existing integrations need a compatibility check rather than an assumption that “1.0” is drop-in. Release notes
The release also packages FP8 key/value caches and a host-memory cache for mixture-of-experts models. Server changes address SSRF, CORS and DNS rebinding, introduce explicit opt-ins for unauthenticated tools and private media URLs, and cancel MCP tool calls when clients disconnect or time out. These are maintainer-reported changes, not an independent security certification. Release notes
Guth take
Local inference is becoming application infrastructure. A visible compatibility boundary makes upgrades easier to reason about, while the server fixes underline that running locally is not itself a security boundary. Developers should pin versions, test their integrations and review network exposure before moving a deployment.
What changed from earlier coverage
Earlier drafts tracked FP8, Vulkan, Metal and SYCL prerelease work. This follow-up records a separate milestone: the numbered 1.0 release, its compatibility policy, retired interfaces and server-hardening bundle. It does not claim those component changes first appeared today.
Evidence limits: no runtime, migration or independent security tests performed. GitHub displays November 13 at 10:20 without an exposed timezone; the announcement independently dates the release November 13. No independent corroboration verified.
Sources and citations
Revision history
Published .