SessionVault

Social media managers, developers, freelancers and support teams juggle several logins on the same sites all day. A browser profile shares one cookie jar, so switching accounts means logging out and back in, or keeping a separate profile for every identity.

Doing it properly is harder than it looks. Modern sign-in flows like Google’s hop across several domains, and an extension has to earn every permission it asks for during Web Store review.

SessionVault gives each tab its own cookie jar using Chrome’s declarativeNetRequest rules. Set-Cookie headers are captured and stored per session, and the right cookies are sent per domain and path on every request.

A page-side script makes document.cookie, localStorage and sessionStorage show the session’s own data before any of the page’s scripts run, so sites behave exactly as if only one account were signed in.