llama.cpp has released build b12057, expanding hardware support to include ROCm 10.0 for Linux and Windows, alongside new binaries for Linux ARM64 Snapdragon devices featuring Adreno GPU and Hexagon NPU acceleration. The update also adds CUDA 13.4 libraries for both x64 and arm64 architectures on Ubuntu and Windows, while temporarily disabling KleidiAI support on macOS Apple Silicon. These changes significantly broaden the range of consumer and enterprise hardware capable of running local large language models without relying solely on NVIDIA GPUs.
Read originalEarlier coverage that leads up to this article, and what followed. Lines connect each piece to the closest one after it, converging here.
llama.cpp Releases · September 30, 2026 · Same story
llama.cpp Releases · October 4, 2026 · Same story
This release quietly fixes a memory allocation quirk on Apple Silicon by switching to vm_allocate, which should stabilize buffer handling across macOS and iOS. More notably, it brings ROCm 10.0 support to both Linux and Windows, finally giving AMD GPU users parity with CUDA builds in the standard distribution. The update also extends CUDA 13 compatibility to ARM64 architectures, broadening the hardware base for high-performance inference. It’s a maintenance-heavy release that solidifies llama.cpp as a cross-platform runtime rather than just a local Mac tool.
This release quietly cements llama.cpp as the universal inference runtime by adding default support for CUDA 13 and ROCm 10.0. NVIDIA users can now leverage newer driver stacks without waiting for separate builds, while AMD GPU owners finally get parity with modern ROCm versions. The inclusion of Snapdragon and OpenVINO binaries further widens the hardware net, though Apple Silicon KleidiAI is notably disabled here. It’s less about new features and more about ensuring no major accelerator is left behind in the local LLM ecosystem.
This release quietly cements llama.cpp as the universal inference runtime by finally supporting CUDA 13 alongside the established CUDA 12 builds. The inclusion of native Snapdragon Linux binaries marks a significant step toward on-device AI for ARM-based mobile hardware, moving beyond just desktop GPUs. While Apple Silicon KleidiAI is currently disabled in this build, the broader platform coverage ensures that developers aren't locked into NVIDIA ecosystems anymore. It’s less about new features and more about removing friction for anyone running newer drivers or edge devices.
This release prioritizes trust and reliability over new features, addressing critical friction points for enterprise users. The most significant addition is a safety check that prompts before sending account emails to external networks, directly tackling data leakage concerns in automated workflows. For developers managing scale, the new gateway admin API cost report provides granular visibility into spend per developer and IdP group, solving a major blind spot in self-hosted deployments. Stability fixes for session persistence, proxy timeouts, and credential handling ensure that long-running agent tasks don't silently fail or leak data.
© Hugging Face BlogHugging Face is solving the regression problem in its massive Transformers library by introducing Model Integration Contracts (MICs). Instead of relying on slow full-scale GPU tests, they shrink real checkpoints into tiny CPU-friendly fixtures that preserve architectural quirks. This approach caught a two-month-old bug in T5’s attention mechanism that standard forward passes missed entirely. It shifts testing from brute-force coverage to precise, reproducible contract verification for every model architecture.
© The Verge AIAnthropic has tightened Claude Code’s system prompt to explicitly forbid recreating specific existing video games, targeting the surge in AI-generated decompilations and ports. The update on Opus 5.5 draws a hard line against IP infringement while preserving the ability to build original titles or genre-inspired projects from scratch. This marks a significant shift in how coding assistants handle intellectual property boundaries, moving from passive compliance to active prevention of direct clones. Developers can now expect stricter refusals when attempting to replicate protected game mechanics or assets.