Key details

  1. Released November 13, 2026, as llama.cpp v1.0.0 and ggml v1.0.0.
  2. Major version bump promised for public C API/ABI incompatibilities; minor for compatible features, patch for fixes.
  3. 35 deprecated llama.h functions removed, along with llama_set_warmup and --defrag-thold.
  4. NextN speculative decoding API promoted to llama.h; state-source function renamed.
  5. FP8 KV caches and a configurable host-memory MoE expert cache added.
  6. llama-server hardens SSRF, CORS, DNS rebinding and tool authentication behaviour.
  7. New OpenAI-compatible /v1/audio/speech endpoint added.

What builders should take away

  1. Pin current builds and test v1.0.0 in staging before upgrading native integrations or service deployments.
  2. Search C/C++ code and launch scripts for removed function names and --defrag-thold, then rebuild against the v1.0.0 headers.
  3. Test llama-server tools and MCP behind non-loopback addresses with an API key; do not casually opt out of authentication.
  4. Audit any CORS proxy or private media URL workflow because local/LAN fetches may now be blocked.
  5. Benchmark FP8 and MoE cache options on actual model, quantization, backend and hardware before claiming memory or throughput savings.

What changed

On November 13, 2026, ggml-org released llama.cpp v1.0.0 and ggml v1.0.0. The maintainers now promise major-version increments for public C API and ABI incompatibilities. This release removes 35 deprecated functions, llama_set_warmup and the defrag-thold option, renames a context-state function, and promotes NextN speculative decoding into llama.h. It also adds FP8 KV caching, host-memory MoE expert caching, new model architectures and an OpenAI-compatible text-to-speech endpoint. Server changes tighten handling of unauthenticated tools, local URLs and CORS proxy requests.

Why it matters

Local AI products often embed libllama or expose llama-server to other services. A documented compatibility contract makes release planning more predictable, but the first 1.0 upgrade deliberately breaks older integrations and configuration flags. Server hardening also changes default behaviour for MCP/tool deployments and local media fetching. Builders should treat this as a tested migration, not merely an upgrade to a stable version number.

Version numbers become a compatibility contract

The maintainer announcement defines major versions for breaking changes to the public C API, minor versions for compatible additions and backend/model support, and patch versions for fixes that preserve the API. The team also says API and ABI incompatibilities will receive major-version bumps. This is a forward-looking maintainer policy, not proof that all downstream packages are already compatible.

The first 1.0 release removes old interfaces

The upstream release removes 35 deprecated llama.h functions plus llama_set_warmup and the defrag_thold context field and command-line flag. llama_set_embd_state_src becomes llama_set_ctx_state_src, and NextN speculative decoding moves from llama-ext.h to llama.h. In-process applications and scripts using these names must be rebuilt or changed; old binaries should not be assumed ABI compatible.

Security defaults can interrupt agent and proxy configurations

The release hardens llama-server against server-side request forgery, DNS rebinding, CORS proxy access to local network addresses and unauthenticated tool exposure. Non-loopback tool/MCP setups now need authentication or an explicit opt-in to unauthenticated tools. Private-address media URLs require a separate opt-in. These changes reduce accidental exposure, but can disrupt previously working trusted-LAN workflows. Avoid restoring permissive defaults without understanding the trust boundary.

New inference options are not universal speedups

The release adds OCP FP8 KV caches, a host-memory MoE expert cache with CPU-share controls, support for new model architectures and a /v1/audio/speech endpoint. FP8 cache footprint and model throughput depend on backend, context, hardware and workload. The release announcement contains capabilities, not an independently established across-the-board speed or cost gain.

What to watch next

  • Downstream binding and package adoption of the 1.x interface contract.
  • Further security guidance for MCP and tool-serving deployments.
  • Independent performance measurements of FP8 KV caches and MoE expert caching across supported backends.
  • Future minor/major release adherence to the published compatibility rules.

Still unclear

  • The semantic-versioning contract is newly introduced; compliance across future releases is untested.
  • Independent production performance and compatibility measurements are limited.
  • The upstream notes describe changes but do not quantify the number of downstream integrations that will break.

Sources

Direct reading behind this dossier.

3 sources
llama.cpp v1.0.0 release notes
ggml-org / GitHub primary

Authoritative release details for API removals, cache features, model support and server hardening.

Discussion

Discussion is reader-contributed. Comments are not part of the BTN dossier or its editorial evidence.

0 visible comments

Join the discussion

Keep comments useful and relevant. Reader contributions may be moderated and are not BTN editorial evidence.

Sign in to comment