demo · v142

Origin Isolation

Pick which origins set Origin-Agent-Cluster: ?1. The simulator groups them into renderer processes the way Chrome 142+ does — same-site origins that didn't opt in still share one process, opted-in origins get their own. Below: the real window.originAgentCluster readout for this page.

origins in play

a.example.com · b.example.com · admin.example.com · other.test

opt-in to Origin-Agent-Cluster

Chrome ≤ 141 (site isolation only)

Chrome 142+ (origin keying for opted-in)

window.originAgentCluster (this page)

—

crossOriginIsolated

—

Renderer-process groupings are simulated. To see real process attribution open chrome://process-internals in Chrome 142+ on a multi-origin site.

relevant API

# Each opt-in origin sends:
Origin-Agent-Cluster: ?1

// Same eTLD+1 siblings that did NOT opt in still share one process.
// Opted-in origins get their own renderer process and their own agent cluster.

relevant API

see also