Session Vault
Menu

Chrome extension

One website.
Separate logins.

Session Vault keeps personal, work, and client accounts apart in different tabs. Same site in the address bar. Different cookie jars. Nothing leaves this browser.

Install from source View source
Manifest V3 Chrome 120+ Local-only data Fail-closed
Not a tab saver

Session Buddy stores windows. This isolates accounts.

Not a new profile

One Chrome. Named sessions on the site you already opened.

Wrong login never

If isolation cannot be proven, the tab stays logged out.

Stays on this device

No cloud account. No telemetry. Export only if you choose.

How it works

A vault per login, not a second browser.

Chrome shares cookies across every tab of a site. Session Vault binds a tab to a session, then serves that session’s cookies on the wire and in the page.

1

Open the site

Click a tab like mail.google.com, then open Session Vault from the toolbar.

2

Create a session

A new tab of that site opens, logged out. Sign in as work, personal, or a client.

3

Repeat for each account

Each session keeps its own jar. Click a row later to open another tab of it.

Product

Popup, manager, and settings — on this device.

Bind the current tab, browse every session, or confirm that nothing is uploaded. These are the same frames used for the Chrome Web Store listing.

Session Vault popup on google.com with Work, Personal, and Client A sessions. Isolation status Isolated.
Popup — switch sessions on the site you already opened
Session Vault manager listing Work, Personal, and Client A sessions for google.com.
Manager — every site and session in one place
Session Vault settings with Local only, No telemetry, and No cloud sync.
Settings — local-only, no telemetry, no cloud sync

Inside the vault

Built to refuse the wrong cookies.

Virtual cookie jars

HTTP cookies live in IndexedDB on this device. Declarative Net Request sets the request Cookie header for that tab only, and strips native Set-Cookie so Chrome’s shared jar does not mix accounts.

Fail-closed by default

Unbound, degraded, or unrecoverable tabs get no authentication cookies. A logged-out page is the safe outcome. Cross-session leakage is treated as a defect, not a warning.

document.cookie, per session

Page JavaScript on a managed tab sees that session’s cookies, not Chrome’s shared jar. localStorage, IndexedDB, and Cache Storage are specified and not virtualized yet.

Temporary sessions

Spin up a disposable login with Alt+Shift+T. When the last tab of that session closes, the jar goes with it.

Be precise

What this is, and what it is not.

Session Vault Tab managers Chrome profiles
Job Isolate logins on one site Save and restore tab sets Whole-browser identity
Same-site accounts Yes, in parallel tabs No Yes, in another window
Data Local jars only Tab lists Separate profile disk
Tradeoff Not a full profile boundary Does not isolate cookies Heavy: duplicate setup

Honesty

Isolation has edges. We name them.

Strong for application cookies and document.cookie. Not a second Chromium profile. Do not imply otherwise in high-assurance work.

Isolated today

Request Cookie headers, native Set-Cookie absorption, and document.cookie — between sessions, on managed sites.

Not yet

localStorage, page IndexedDB, Cache Storage, BroadcastChannel, and Web Locks. Specified. Not virtualized in this build.

Not isolated

Existing Service Workers, SharedWorker, the browser HTTP cache, history, bookmarks, Chrome sync, TLS client certs, the password manager, fingerprints, and your IP address.

Keyboard

Stay in the tab. Switch the jar.

AltShiftS

Session switcher

Open the popup for the current site.

AltShiftT

Temporary session

New logged-out tab. Jar deleted with the last tab.

Commands

Next, previous, duplicate

Bind the current tab, or open this page in another session.

Privacy

Your sessions never leave this machine.

No product analytics. No cloud account. No remote fonts in the extension. Host access is requested when you isolate a site — not for every website at install. Read the privacy policy and permissions notes.

  • Session metadata in chrome.storage.local
  • Tab bindings in chrome.storage.session
  • Cookie jars in extension IndexedDB
  • No upload unless you export a file yourself

Install

Load the unpacked build.

The Chrome Web Store listing is not published yet. This is a development build: cookie isolation is in, page-storage virtualization is not. Build locally, then load the folder in chrome://extensions with Developer mode on.

  1. Run the commands in the terminal
  2. Open chrome://extensions
  3. Enable Developer mode
  4. Load unpacked → .output/chrome-mv3
git clone https://github.com/Mohpfd96/session-vault.git
cd session-vault
pnpm install
pnpm build