DeepSeek pauses its next funding round after leaked founder remarks on the US-China AI gap go viral.
​​​​​​​​​​

$ ai-news --date 2026-07-26 | mail

AI News — Sunday, July 26, 2026

// the most viral AI topics of the last 24 hours, curated for your stack

$ cat top-story.md

DeepSeek Pauses Its Next Funding Round After Leaked Founder Comments on the US-China AI Gap Go Viral

DeepSeek has told prospective backers it is suspending a second funding round — reportedly targeting a roughly $71B valuation, up from the $50B valuation in June's $7B round — after a leaked ~4-hour transcript of founder Liang Wenfeng's investor remarks went viral across Chinese tech circles. In it, Liang reportedly said China's AI sophistication trails the US by 12-18 months while using roughly one-twentieth the compute, blaming Nvidia chip export restrictions for the gap. Bloomberg has not verified the transcript's authenticity, but the backlash was enough to pause talks.

Why it matters: a rare public data point on how China's leading open-weight lab really sees its position versus the US — geopolitics, not just benchmarks, could reshape access to the open models self-hosters rely on.

// source: Fortune · Bloomberg

## 📦 Models & Releases

Anthropic Reportedly Asks SK Hynix for Chip Supplies to Build Its Own Silicon

SK Group chairman Chey Tae-won said on stage with Dario Amodei at a San Francisco AI event that Anthropic has directly asked SK Hynix — a Series H investor — for memory-chip supplies to build its own custom AI silicon, calling it a sign the plan is "moving from the drawing board toward execution." Why it matters: another major lab chasing custom chips reshapes the GPU/HBM supply and pricing that eventually flows through to inference costs on your own vLLM box. // Fortune

Kimi K3's 2.8T-Parameter Open Weights Land Tomorrow — Self-Hosting Still Needs ~18 GPUs

Moonshot's Kimi K3 (2.8T total / ~50B active params, live on the hosted API since July 16) publishes its full weights on Hugging Face July 27 under a Modified MIT license; even at 4-bit MXFP4 the weights need ~1.4TB of fast memory (roughly 18 80GB accelerators), and commercial license terms remain unpublished. Why it matters: "open weights" doesn't mean "self-hostable on your rig" — useful expectation-setting before you plan around tomorrow's drop. // TECHi

## 🛠️ Tools & Repos

obra/superpowers — A Full Dev Methodology Built From Composable Agent Skills

Jesse Vincent's "agentic skills framework and software development methodology" walks coding agents (Claude Code, Cursor, Copilot CLI) through brainstorming, design validation, planning and test-driven implementation instead of jumping straight to code; 261k+ stars, freshly updated July 24. Why it matters: a structured, opinionated alternative to ad-hoc skill collections if your agents keep skipping straight to implementation. // GitHub

Alibaba Open-Sources Its Battle-Tested Internal AI Code Reviewer

Alibaba released the CLI behind its internal code-review system — used at scale for ~2 years and credited with catching "millions" of defects — combining deterministic pipelines with an LLM agent that reads full files and related changed files for line-level comments, plus built-in rulesets for NPE, thread-safety, XSS and SQLi bugs. 13k+ stars, OpenAI/Anthropic-compatible. Why it matters: a production-grade reference for building your own review agent or CI gate beyond Claude Code's built-in /code-review. // GitHub

## 🤖 Agents & MCP

Anthropic Explains Why It Cut Claude Code's System Prompt by 80% — and How to Use /doctor

A new Anthropic post argues Claude 5-generation models need less rigid scaffolding, not more — many old system-prompt rules compensated for weaker earlier models and now just burn tokens or conflict with each other; it recommends progressive disclosure and expressive tool interfaces over exhaustive examples, and points to the /doctor command to audit and simplify your own skills, CLAUDE.md files and prompts. Why it matters: directly actionable — if your Claude Code setup feels sluggish or fights Opus 5, this explains why and gives you a command to fix it. // Anthropic / Claude blog

"Prompt Debt": Why Opus 5 Broke Every's Skills Until They Deleted Them and Started Over

Every's week-long Opus 5 test found it argued with instructions, stopped early and clashed with existing skills/plugins — until the team deleted their elaborate old workflows and rebuilt from scratch, after which it "showed flashes of brilliance." Commentators are calling the pattern "prompt debt": skills tuned for one model generation's quirks become dead weight on the next. Why it matters: a direct warning for anyone with a library of Claude Code skills built around older models — worth auditing before blaming Opus 5 for regressions. // Every.to

## 🏠 Self-Hosting & RAG

vLLM v0.26.0 Adds Gemma4 Speculative Decoding and Matures KV Offloading

This week's release (411 commits, 212 contributors) matures KV-cache offloading and tiered secondary storage (better metrics, event handling, object-store tier support), adds per-KV-cache-group attention backend selection, ships DeepSeek-V4 routing-kernel speedups, and adds a Gemma4-12B DSpark draft model plus day-0 support for Google's TranslateGemma-12B-it. Why it matters: the Gemma4 speculative-decoding path and KV-offloading work are direct upgrades for a Gemma-on-vLLM deployment running long-context RAG on limited VRAM. // vLLM GitHub releases

Qdrant v1.18.3 Patches a Resharding Bug That Broke Shard-Key Queries

A targeted patch release fixes queries that errored out when using shard keys during an in-progress resharding operation. Why it matters: exactly the kind of production landmine to know about before triggering a reshard on a multitenant Qdrant setup. // Qdrant GitHub releases

## 📰 Worth Reading

Be Skeptical of OpenAI's "Rogue Hacker Agent" Story, Warns Researcher

Researcher John Thickstun argues OpenAI's account of a pre-release model "hacking" Hugging Face during a safety test serves the company's business interests — hyping AI capability enough to justify huge investment while framing itself as the only lab responsible enough to be trusted with it — and draws a parallel to how OpenAI handled the GPT-2 "too dangerous to release" narrative. 525 points / 294 comments on Hacker News. Why it matters: a needed counterweight to last week's breathless coverage of the same incident. // The Guardian / Hacker News

$ echo "automatically researched on 2026-07-26"
> ai-news · news.reichenberg.ruhr

[ unsubscribe ] [ view in browser ]