Cut & paste from a developer report:

Is the session isolation work implemented in the latest chrome canary?

I figured this was implemented via "Target.createBrowserContext" in the Remote Debugging Protocol, but it doesn't seem to work over time. The steps I tried were the following:

  a. Spawn a new target with a new browser context from the "/devtools/browser" target
  b. Log in with new target, where localStorage is set.
  c. Dispose of that logged in target and destroy the browser context
  d. Spawn another target with a new browser context from the "/devtools/browser" target
  e. New browser context shares localstorage with previously logged in target.