Coding Tools
llama.cpp b11018 adds CUDA 13 and ROCm 10 builds
llama.cpp Releaseshigh confidence
Why it matters
- →Enables inference on GPUs requiring CUDA 13 or ROCm 10 drivers.
- →Removes the need to downgrade system libraries for local model testing.
- →Expands support for Intel Arc (SYCL) and AMD hardware in the standard build pipeline.
llama.cpp has released build b11018, expanding hardware support to include CUDA 13 (versions 12.8 on Linux, 13.3/13.4 on Windows) and ROCm 10.0 for AMD GPUs. The update also adds SYCL FP32/FP16 builds for Intel Arc and OpenVINO support across Linux and Windows platforms. macOS KleidiAI builds are currently disabled in this release. This version allows users to leverage the latest GPU drivers without downgrading, ensuring compatibility with modern NVIDIA and AMD hardware configurations.
Read originalMore from llama.cpp Releases
Coding Toolscoding
llama.cpp b11017 adds CUDA 13 and ROCm 10 builds
This release quietly extends llama.cpp's hardware support to the latest NVIDIA and AMD stacks. By shipping native binaries for CUDA 13 and ROCm 10, it ensures compatibility with newer GPU architectures without requiring users to compile from source. The inclusion of both CUDA versions side-by-side is a pragmatic move for enterprise environments managing mixed infrastructure. While no new model formats are introduced, this update keeps the runtime relevant as hardware vendors push their latest drivers.
llama.cpp Releases
Coding Toolscoding
llama.cpp b11019 fixes embedded GGUF loading bugs
This release patches a subtle but critical bug where embedding a GGUF file inside another container caused tensor data corruption due to misaligned memory mapping. The fix ensures the data section is aligned relative to the GGUF header rather than the outer file offset, preventing silent errors that could ruin inference results. It also adds support for loading LoRA adapters via FILE pointers and disables mmap with a warning when alignment issues are detected. This stabilizes llama.cpp for complex packaging scenarios where models are bundled within larger archives or custom formats.
llama.cpp Releases
Coding Toolscoding
llama.cpp b11020 adds DeepSeek V3.2/V4 parser support
This release fixes a critical parsing gap for DeepSeek's latest models in llama.cpp. By adding message delimiters to the V3.2 and V4 parsers, it ensures chat history is handled correctly during inference. The update also ships binaries for CUDA 13.3/13.4 and ROCm 10.0, keeping hardware support current. KleidiAI on Apple Silicon remains disabled in this build, a notable omission for Mac users seeking optimized performance. It’s a necessary maintenance release that keeps local DeepSeek usage stable.
llama.cpp Releases
More in Coding Tools
Coding Toolscoding
Claude Code v2.1.275 patches stability and sync
This release stabilizes Claude Code by fixing crashes that occurred when resuming sessions with malformed transcripts or memory files. It also improves the developer experience by syncing skills and plugins from your claude.ai account to terminal sessions, ensuring consistency across environments. Security is tightened by preventing install scripts from running on npm-sourced plugins, while usability sees gains in artifact publishing and image handling. The update addresses critical edge cases that previously broke workflows, making the tool more reliable for daily use.
Claude Code Releases
Coding Toolscoding
Claude Code v2.1.276 fixes proxy regression
Anthropic quietly patched a critical regression in Claude Code that broke all API requests for users routing traffic through proxies or gateways. The issue stemmed from an invalid input tag 'advisor_20260301' introduced in the previous version, effectively locking out enterprise and custom infrastructure setups. This fix restores basic functionality for developers who cannot connect directly to Anthropic's endpoints, highlighting the fragility of recent CLI updates.
Claude Code Releases
© GitHub ChangelogCoding Toolscoding
GitHub Copilot adds feature-level engagement metrics
GitHub is finally giving enterprise admins the granular data needed to measure actual AI adoption rather than just license utilization. The new dashboard and API breakdowns distinguish between passive code reviews triggered automatically and active agent edits or CLI usage, revealing which tools developers actually integrate into their daily workflows. By tracking rolling 28-day populations per adoption phase, organizations can now pinpoint exactly where training is needed instead of guessing based on broad engagement numbers. This shift from counting seats to measuring specific feature interaction marks a maturation in how AI productivity is quantified at scale.
GitHub Changelog