— Chrome extension

SplitSession

Same site. Separate logins.

Works like Firefox containers: several accounts of one site stay signed in at once, in different tabs of one profile.

Chrome Web Store Download GitHub

Version 0.1, beta. Free, MIT licence.

Two tabs of the same site as the two halves of Chrome's split view: one signed in as Northwind Studio in the Work container, the other as Dana W. in the Personal container. — Chrome’s split view: two accounts of one site side by side, each half in its own container with its own login.

What it does

ContainersA name, a colour and a cookie jar each. Export and import as JSON; cookies stay out unless you tick the box.
IsolationCookies, localStorage, IndexedDB and more are kept apart per container. Links and popups opened from a container tab stay in it.
Tab groupsEach container is a Chrome tab group in its colour, synced both ways. A split pair of two containers leaves the groups, so each side keeps its login.
Domain rulesAlways open a site in container X, or ask.
RestoreAfter a restart, tabs return to their containers. A tab that cannot be matched with certainty waits in the popup and sends nothing to the site.
Strict mode, optionalRemoves service workers so none can answer a container tab with your regular logins. Push notifications stop working.

AI agents (Full)

An optional local MCP server lets your own agent (Claude Code, Codex, Cursor and others) list your tabs with their containers and operate them: snapshots, trusted clicks and typing, screenshots, console and network.

Off by default, one all-or-nothing switch. While it is on, the agent can act in every tab, signed-in pages included.

npx splitsession-bridge install

Then turn on “Agent bridge” under Settings, For AI agents.

Tools, security model, client options · npm

Full edition only

How it works

Create a container in the toolbar popup.
Open the same site in a second tab.
Sign in as someone else. Both accounts stay logged in.

How isolation works

Lite / Full

One codebase, two builds. Lite is containers only. Full adds the optional local agent bridge. The bridge code is not compiled into Lite, and the Lite build fails if any of it, or a Full-only permission, ends up in the bundle.

	Lite	Full
Containers, isolation, tab groups, rules, strict mode, restore, export	yes	yes
Agent bridge (MCP), off by default	no	yes
Extra permissions	none	`nativeMessaging`, `debugger`
Get it from	Chrome Web Store, GitHub Releases	GitHub Releases

Install

Lite installs in one click from the Chrome Web Store. Full, or Lite if you prefer, installs from a GitHub release:

Download and unzip splitsession-lite-<version>.zip or splitsession-full-<version>.zip from Releases.
Open chrome://extensions and turn on Developer mode.
Choose Load unpacked.
Select the unzipped folder, then pin the toolbar button.

Keep one copy of SplitSession per Chrome profile (Store or GitHub, Lite or Full).

Animation: download the zip from a GitHub release, unzip it, open chrome://extensions, turn on Developer mode, choose Load unpacked, select the folder and pin the toolbar button.

Limits & privacy

It separates accounts, nothing more.Not a privacy tool, not a sandbox. The HTTP cache, HTTP auth, browser fingerprint, saved passwords and history are shared. One residual hole is documented: same-origin frames and popups during navigation.
Beta.Tested against a local stand, not on many real sites. Some sites may notice two sessions from one browser.
Sends nothing anywhere.No account, analytics or telemetry; no network requests of its own. It asks for access to all sites because rewriting request headers per tab needs it. Data sits unencrypted in chrome.storage, like Chrome’s own cookies.

Privacy policy · All limits · How isolation works