llama.cpp ships full MCP support — local models just got tool use with zero cloud dependency.
Top Signal
llama.cpp lands full MCP support — local agents get native tool use
platform change
r/LocalLLaMA
After extended work led by contributor ngxson, llama.cpp has merged complete Model Context Protocol support across all transport types, including stdio servers. HTTP-based MCP servers were already wired in, but stdio required deep plumbing — that gap is now closed. What this means in practice: any local model running in llama.cpp can now connect to MCP tool servers (file systems, databases, web search, code execution) without routing a single token through a cloud API. For builders running agents locally — for cost, privacy, latency, or air-gap reasons — this removes the last major capability gap versus hosted model APIs. MCP has become the de facto tool-use standard; llama.cpp reaching parity means local-first agent architectures are now a first-class option, not a compromise. Action: pull latest llama.cpp and wire in your existing MCP servers today.
Read more →
Fast Signals
Anthropic publishes new context engineering rules for Claude 5 generation
workflow
HN Front Page, Simon Willison
Anthropic's blog details updated prompting patterns specific to the Claude 5 model family — system prompt structure, tool definitions, and memory management guidance that diverge from prior generations. Separately, Boris Cherny flagged a buried detail in the Opus 5 system card: it's Anthropic's least prompt-injectable model yet, with measurably better resistance to adversarial inputs. If you're building externally-exposed agents or chatbots, test that property before assuming you still need additional guardrail layers.
Link →
Inflect v2: complete end-to-end TTS in 4M and 10M parameter models
new tool
r/LocalLLaMA
A community release of two full TTS models — 4M and 10M parameters — that run locally with no external dependencies. At these sizes, speech synthesis becomes embeddable in virtually any edge device or mobile app at near-zero inference cost. Evaluate if you're building voice UX or accessibility features that need to work fully offline.
Link →
LFM 2.5 230M runs at 1440 tok/s entirely in-browser via custom backend
emerging signal
r/LocalLLaMA
Liquid Foundation Models' 230M model is running at 1440 tokens/second in-browser through a custom WebAssembly/WebGPU backend with no server involved. This sets a new practical bar for browser-native inference. If your product targets users who want zero data-leaves-device guarantees, this class of approach is maturing into a real deployment option.
Link →
Gemma 4 26B runs on iPhone 17 Pro via model paging
emerging signal
r/LocalLLaMA
Community demo shows Gemma 4 26B (4B active parameters, MoE) running on iPhone 17 Pro using model paging — swapping layers from flash storage on demand, trading latency for above-RAM model size. Not a finished product, but a concrete technique reference for builders targeting on-device inference on next-gen iOS hardware.
Link →
Kimi K3 exploits latest unpatched Redis CVE
emerging signal
HN Front Page
Kimi K3 successfully exploited a live Redis server vulnerability, per an HN front-page thread. This follows last week's report of K3 finding 5 real bugs in post-quantum crypto libraries. K3's offensive security reasoning capability is becoming a repeating signal — if you're building security tooling or need a model that can reason through exploit chains, it's worth a closer look.
Link →
Ruff v0.16.0 enables new default lint rules — CI pipelines breaking
platform change
Simon Willison
Astral shipped Ruff v0.16.0 on July 23rd with additional rules turned on by default. Simon Willison flagged it today after his CI jobs started failing on previously-passing code. If you have unpinned Ruff in any Python project's CI, audit your config against the new rule IDs before your next push breaks the build.
Link →
Radar
AMD releases Instella-MoE-16B-A3B open-weight model
AMD uploaded a 16B MoE (3B active) with a Think reasoning variant to HuggingFace. AMD entering the open-weight model publishing space is worth tracking — particularly if you build on AMD hardware and want a model that's been tuned for that stack.
Link →
SupraLabs drops 5M reasoning examples for tiny SLM fine-tuning
SupraLabs released reasoning-corpus-4K-5M-v1, a 5-million-sample dataset designed to teach small language models chain-of-thought reasoning. If you're fine-tuning sub-7B models for structured reasoning, this is a direct training resource worth evaluating.
Link →
Postgres LISTEN/NOTIFY scalability deep-dive from DBOS
DBOS published benchmarks showing PG LISTEN/NOTIFY scales significantly better than its reputation suggests, making it viable as a lightweight event bus for agent workflows. Worth reading before reaching for Redis or a dedicated queue for low-to-medium throughput notification patterns.
Link →
Convergence Watch
open-weight ai regulation
TRENDING
9 mentions across HN Front Page, r/LocalLLaMA
The pro-open-weight coalition hardened today: NVIDIA, Microsoft, Meta, HuggingFace, OpenAI, and now Google have all publicly signed or endorsed the letter against restrictions. Anthropic is the notable holdout. The near-term risk for builders is targeted restrictions on Chinese open-weights specifically — not blanket open-weight bans. Lobby math currently favors continued access.
claude opus 5
4 mentions across HN Front Page, Simon Willison
Yesterday's launch surfaces new builder-relevant detail today: Opus 5's prompt injection resistance is quantifiably better than prior models per the system card. If you're running any externally-facing agent pipeline, this property warrants empirical testing — it may reduce the guardrail overhead your current stack requires.
kimi k3
2 mentions across HN Front Page
K3 keeps appearing in offensive security contexts — Redis exploit today, post-quantum crypto bugs last week. A pattern is forming: K3 has genuine vulnerability-reasoning depth that distinguishes it from general-purpose coding models. Watch this space if security tooling is in your roadmap.