Urgent.News

What's breaking now, across hundreds of outlets.

Tech

Real URLs, Synthetic Pages: Inside Chrome's Mirror Dimension

On 19 November 2026 at 17:00 UTC, Google's security blog published a post from Chrome's AI Security team, written by Aaron Selya and Charles Qian. There is no CVE, no list of affected versions, no patch diff, no remediation deadline. It opens with a different claim: Chrome already ships agentic browsing ( auto browse ), and to test the defenses around it the team built a synthetic replica of the…

On November 19, 2026, Google's Chrome AI Security team announced a new project in their security blog. The team, led by Aaron Selya and Charles Qian, described a synthetic replica of the web dubbed the "mirror dimension." The team built this mirror dimension to test defenses against agentic browsing, a feature they claimed was already built into Chrome.

The post was notable for its focus on the infrastructure needed to test browser agents, rather than the vulnerabilities they could exploit. The team explained the challenges of testing agents on the open web, noting that real users don't provide URLs and test environments often assume they do. They also highlighted the scale requirement – thousands of read and write actions across hundreds of websites, continuously – and the risks of using the open web for evaluation, such as the web's constant changes and the potential for an unconfined agent to cause real damage.

The solution proposed was a synthetic site infrastructure – "the mirror dimension" – that would maintain local state, handle real URLs and multi-page flows, and provide a safe, repeatable environment for testing. This involved using gVisor, a Linux-like application kernel running in user space, to isolate the agent and intercept its network requests.

The proxy component of this system would mint TLS certificates on the fly and route requests to the synthetic site. The post acknowledged the challenge of intercepting connections in a way Chrome itself blocks, but suggested minting TLS certificates at startup using a custom root CA preinstalled in the sandbox as a solution.

Rewritten by urgent.news; may contain errors — check the original.

Read the original at dev.to →

Report a problem with this story

More in Tech

More from Saturday 21 November →