MultiLogin TabsSession isolationMultiple accounts,
one browser window.
Run multiple accounts on the same site at once — no incognito, no separate Chrome profiles. Assign each tab a named session and it gets a fully isolated environment.
Cookies
HTTP (Set-Cookie) and JavaScript (document.cookie) alike — each tab sends only its own.
localStorage
Proxied under a per-session key namespace. Every app sees only its own stored data.
IndexedDB
Database names are prefixed per session — each session keeps its own databases.
Cache Storage
Cache names isolated per session. PWA caches and offline data stay fully separate.
Open tabs
Open two or more tabs of the same website.
Assign a session
Name each tab a session — Admin, User1, Tester.
Stay isolated
Each session gets a fully isolated environment — accounts never interfere.
Let a Claude agent run every account at once
Point a browser MCP (Playwright / Puppeteer over CDP) at a Chrome that has MultiLogin Tabs loaded, and a Claude agent inherits the per-tab isolation automatically. One agent can drive several accounts in parallel — each in its own sealed session, cookies never crossing over.
- Isolation the agent can trust. Every automated tab is a private session — the agent won’t leak one account into another.
- Parallel accounts, one window. Assign the sessions, aim the MCP browser at the tabs, and the agent works them all at the same time.
- Any MCP browser. No bespoke server — the extension just loads in the Chrome your agent already drives.