llama.cpp has released build b11146, expanding hardware compatibility for local inference. The update adds native support for CUDA 13.4 on Ubuntu and Windows for both x64 and arm64 architectures, alongside ROCm 10.0 builds. A key addition is the first official Linux arm64 binary targeting Snapdragon platforms, supporting CPU, Adreno GPU, and Hexagon NPU acceleration. The release also includes updates for openEuler with ACL Graph support for Huawei Ascend chips. macOS KleidiAI builds are currently disabled in this version.
Read originalThis release targets a specific bottleneck in long-context inference by optimizing the sparse flash attention prefill step for NVIDIA GPUs. By templating kernels to unroll loops at compile time, batched sparse operations drop from 586 microseconds to 244 microseconds on 49k context windows. This isn't just a generic speed bump; it makes handling very long documents significantly more efficient for users relying on sparse attention mechanisms. The change is already baked into the standard CUDA builds, requiring no special flags.
This release quietly cements llama.cpp as the universal inference runtime by finally bringing first-class ROCm 10.0 support to both Linux and Windows. AMD GPU users no longer need workarounds, effectively closing a long-standing parity gap with NVIDIA's CUDA ecosystem. Equally notable is the new Linux arm64 build targeting Snapdragon chips, which unlocks local LLM execution on high-performance mobile hardware via CPU, Adreno GPU, and Hexagon NPU acceleration. While KleidiAI on Apple Silicon has been disabled in this specific binary set, the broader platform expansion signals a shift toward heterogeneous computing that extends well beyond traditional desktop GPUs.
This release quietly solidifies llama.cpp’s position as the universal inference runtime by adding explicit ROCm 10.0 builds for both Linux and Windows. The inclusion of CUDA 13.4 alongside the existing 12.x variants ensures compatibility with the latest NVIDIA driver stacks without forcing users to stick to older libraries. More importantly, the new backend testing infrastructure means these diverse hardware configurations are now validated systematically rather than left to chance. This reduces fragmentation for developers running on AMD or newer NVIDIA cards who previously had to troubleshoot build issues manually.
This release stabilizes Claude Code's core reliability by fixing persistent bugs in session resumption and prompt caching that previously caused data loss or infinite loops. It also tightens enterprise security with new Bedrock upstream support for IAM role assumption and mandatory guardrail application. The update addresses critical edge cases like proxy stream drops and oversized tool calls, ensuring smoother operation in complex development environments.
© Duncan RogoffAnthropic has published an official guide on optimizing Claude Code with the new Opus 5.5 model, shifting focus from raw capability to engineered workflow. The playbook details specific prompting habits that reduce latency and cost while increasing autonomy during long coding sessions. This moves beyond generic advice, offering concrete strategies for developers who rely on agentic coding tools for complex tasks. It signals a maturation in how enterprise-grade AI assistants are integrated into daily engineering practices.
© GitHub ChangelogGitHub has permanently removed Node 20 from its hosted runners, forcing all JavaScript actions to run on Node 24. The safety net of the unsecure node opt-out is gone, meaning workflows relying on older action versions will break immediately. This shift eliminates legacy runtime support and introduces compatibility constraints for macOS 13.4 and ARM32 architectures. Maintainers must update their action metadata now, while workflow users need to upgrade dependencies to avoid CI failures.