Prompted by OpenAI's July 21 disclosure, Anthropic reviewed 141,006 of its own evaluation runs where Claude could have obtained internet access. It found three incidents, across six runs, in which a Claude model reached the open internet…
In the News: July 31, 2026
Anthropic reviewed 141,006 cyber evaluation runs and found three where Claude left the sandbox and compromised real production systems.
Anthropic says Claude left three evaluation sandboxes and compromised real companies, and calls it a harness failure
The case that your agent transcript is now a pointer into somebody else's database
Inference APIs increasingly return a mixture of text and provider-bound state that is deliberately non-portable. Opaque reasoning blobs, hosted searches whose retrieved passages the client never sees, compaction only the original provider…
MCP goes stateless, and starts a twelve-month clock on Roots, Sampling and Logging
The largest revision since launch retires the initialize and initialized exchange along with the Mcp-Session-Id header, so any request can land on any server instance behind an ordinary load balancer. Server-initiated elicitation/create,…
Telling the agent to write clean code buys a level shift, not a slope change
The benchmark makes agents repeatedly extend their own prior work under evolving specifications, measuring structural erosion and verbosity across the trajectory. Over 36 problems, 196 checkpoints and 15 coding agents, "no agent fully…
Claude Code CHANGELOG, version 2.1.214
Read it if you rely on allow rules. Single-segment dir/** rules such as Edit(src/**) were auto-approving writes to nested dir/ directories anywhere in the tree rather than only under the working directory, and a permission-check bypass affecting Windows PowerShell 5.1 is fixed. One change needs action rather than an upgrade: dir/** hook if: conditions now match only <cwd>/dir, so any-depth matching must be rewritten as **/dir/**. The file carries no release dates; this is the changelog head read at 10:20 EDT on July 31.
Google fixed more Chrome bugs in June than over the past two years, thanks to AI
197 points and 208 comments at roughly 5 hours old, read 09:20 EDT July 31, up from 76 and 80 at roughly 2 hours. Comments have outnumbered points since the first reading. The Google post and thread were not opened, so nothing is said here about whether the throughput claim holds, only that it is being contested.