Matthew Green reported the replay flaw to Anthropic, OpenAI, and Google in May and was dismissed. The labs' position: no meaningful security implication. Then Alexander Panfilov and collaborators at ELLIS Institute Tübingen did the work anyway, injecting a stronger model's encrypted reasoning trace into a weaker sibling, jailbreaking the sibling, and recovering the frontier model's hidden chain-of-thought in plaintext, without touching the stronger model or tripping its anti-distillation safeguards. The gap between "no security implication" and "live decoded examples on a public site" is not a gap in the math. It is a gap in who was paying attention.

The two camps here are not researchers versus labs. They are people who treated the encryption as a trust boundary and people who treated it as an engineering artifact. The labs built a system where encrypted blobs carry no binding to session, user, or model, and called that sufficient. The researchers took the same artifact and used it as a relay. Anthropic is now shipping watermarks and provenance metadata for Claude outputs starting August 2026, BlkSeal is building revocable signing for AI responses at creation time. Both moves assume the content layer cannot be trusted on its own. The labs that dismissed Green's report in May are now operating in a world where that assumption has been demonstrated in public. Those two positions don't end in the same place.

Top developments

  • Johns Hopkins cryptographer Matthew Green reveals that frontier AI APIs return encrypted reasoning blobs that can be replayed across sessions, users, and models: Anthropic, OpenAI, and Google send encrypted chain-of-thought blocks back to API clients, and those blocks carry no binding to the session, user, or model that produced them. ELLIS Institute Tübingen PhD researcher Alexander Panfilov and collaborators extended this finding: by injecting a stronger model's encrypted trace into a weaker sibling and jailbreaking that sibling, they recover the frontier model's hidden reasoning in plaintext without attacking the stronger model directly or triggering its anti-distillation safeguards. Johns Hopkins cryptographer Matthew Green had reported the replay flaw to the labs in May, but they dismissed any security implications. The Stolen Thoughts project site includes live decoded examples and a "guess the model" game.

  • Company Offering '100% Human-Written, Never AI' Medical Research Is Entirely AI: 404 Media's Emanuel Maiberg investigated Research Gold, a service selling peer-review-ready medical manuscripts and systematic reviews while claiming human-only authorship. The PhD reviewers listed on its site are AI-generated personas that don't exist, other named staff are real people whose identities are used without permission, and every customer touchpoint, phone, email, and chat, is handled by AI. The story lands as journals already struggle with AI-generated papers and compromised peer review.

Videos worth watching

Announcements & releases

Worth reading

  • H3-metal, Native MiniMax-H3 inference for Apple Silicon: Redis creator Salvatore Sanfilippo built h3.​c, a pure-C Metal-accelerated inference engine for MiniMax's H3 video model on Apple Silicon Macs. On an M5 Max with 128GB unified memory it generates a roughly 9-second clip in minutes rather than the hour-plus needed by GGUF-based ComfyUI pipelines. The model can also run on 64GB machines with small code changes, though throughput will be limited by memory bandwidth (300 GB/s on M-Pro chips vs. 600 GB/s on M-Max), and weight streaming from SSD instead of RAM adds another bottleneck.

  • Apple Silicon and macOS VMs: 11, 16× Faster LLM Inference with Llama.​cpp: macOS VMs built on Apple's Virtualization.​framework expose only a conservative Metal GPU profile to guest processes, causing llama.​cpp to run slower, older GPU code paths. The Cua team built a process-scoped Metal capability shim that intercepts and upgrades the capability answers for a single guest process, letting llama.​cpp select newer Metal kernels without affecting the rest of the VM. Benchmarks on an M1 Ultra host show 7.2× faster prompt processing and 14.5× faster token generation. The work is open-sourced under the same permissive license as Lume, M1 Pro and M3 Pro results are not yet available.

  • llama.​cpp gets an official home at llama.​app: The local-inference engine that runs open-weight models on consumer hardware now has a polished landing page with one-line install, docs, and a model browser. GGML, the team behind llama.​cpp, joined Hugging Face in February 2026, so HF now stewards the project. The HN discussion highlights practical tips: llama-server supports multi-model configs via a single ini file, quantized Qwen3 MoE models punch above their weight for coding tasks, and llama.​cpp pulls models directly from Hugging Face.

  • What I learned by putting GitHub Copilot behind a MitM proxy: Rafael, writing for the Lighthouse AI newsletter, routed VS Code's Copilot traffic through mitmproxy to see exactly what gets sent. Because Copilot runs inside Electron (which uses Chromium's TLS stack), certificate pinning is not an obstacle, making interception straightforward. Key findings include how Copilot assembles its context window from recent edits and session memory via its Chronicle tool, how auto model selection is negotiated at the network layer, and how much telemetry flows beyond what your prompts contain. Readers in the Hacker News discussion note that eBPF uprobes offer an even cleaner bypass for tools that bundle a statically compiled BoringSSL, letting you capture plaintext right before encryption without fighting any proxy.

Discussions & takes

  • Developers are questioning whether Claude is worth it as trust in Anthropic erodes: A developer thread argues that Claude Code's momentum is stalling as users hit low rate limits, notice quality regressions in newer models, and feel condescended to by Anthropic's communications. The worry is that complaints have shifted from "which Claude model is best" to "should I switch to GPT or go local", a sign of eroding brand loyalty rather than healthy competition among models.

  • RTK is a Rust CLI proxy that cuts 60-90% of terminal token noise before it reaches your coding agent's context window: Coding agents like Claude Code waste large chunks of their context window on repetitive build logs, progress bars, and boilerplate output. RTK (Rust Token Killer) wraps common commands like git status or cargo test, filters the noise, and returns only useful output, keeping the agent's reasoning focused and sessions longer. It is a single Rust binary with no dependencies and is open source under Apache 2.0.

  • Why Go Is an Ideal Language for AI-Assisted Software Engineering: A Google Developers Blog post argues that as AI agents write more code, the bottleneck shifts from writing to reviewing, and Go's explicit style, mandatory formatting, strong standard library, built-in tooling (fuzzing, profiling, tracing), and strict backward compatibility make AI-generated Go easier to audit and maintain than most alternatives. Commenters push back hard: some cite Tencent's AutoCodeBench multilingual benchmark, which ranks Elixir near the top for LLM-generated code quality, while others argue that languages with stronger type systems (Rust, Haskell) or larger training corpora (JS, Python) are better fits for agentic workflows.

  • Nvidia's Risky Business: Stratechery's Ben Thompson draws a historical parallel to Jay Cooke's 1870 Northern Pacific Railway gamble to map out Nvidia's compounding risks: CUDA's software moat is real but brittle, hyperscalers are investing heavily in custom silicon, and China exposure adds geopolitical fragility. The Hacker News discussion digs into whether Google's TPU strategy could finally crack CUDA's grip, and what it would take for an alternative to achieve the same ecosystem depth.