Chrome

$2,283. That’s what it cost Mohan Pedhapati, CTO of security firm Hacktron, to build a fully functional 12-phase exploit chain targeting Chrome’s V8 JavaScript engine — using Claude Opus 4.6 as his primary engineering partner. No prior exploit code fed to the model. No exploit framework to scaffold from. Just a researcher, an API key, and roughly 20 hours of human effort across 1,765 requests and 2.33 billion tokens. The result was working Remote Code Execution (RCE). ...

When Chrome ships a feature, it ships to roughly 3.4 billion browsers simultaneously. That’s what makes Chrome 146’s native Model Context Protocol (MCP) support such a significant — and potentially consequential — development for the agentic AI ecosystem. What WebMCP Actually Is MCP, for those who need the refresher: it’s Anthropic’s open protocol for connecting AI models to external tools and data sources in a standardized way. The “Web” prefix in WebMCP specifically means browser sessions — live, authenticated, cookie-bearing browser sessions. ...

OpenClaw shipped v2026.3.13 early this morning, and it’s a meaningful release for anyone running browser automation, using OpenClaw on mobile, or hitting dashboard performance walls on heavy agentic runs. The headline feature is the Chrome DevTools Protocol (CDP) attach mode — a native integration that lets OpenClaw connect directly to a signed-in live Chrome session for real-time debugging and automation. That’s a significant capability addition: instead of spinning up an isolated browser profile, you can now attach to the Chrome instance you’re already using, complete with your active sessions, cookies, and extensions. ...