SplitSession: Multiple Logins per Site

Use several accounts of the same site side by side in one Chrome profile. Optional local AI-agent bridge, off by default.

SplitSession: Same site, separate logins. Keep several accounts of one website signed in side by side in one Chrome profile. Create a named, coloured container, open a tab in it and sign in. Use another container for another account. Tabs in one container share its cookies and site storage; different containers stay separate. Links and pop-ups opened from container tabs stay with them. Ordinary tabs keep your usual logins. FEATURES - Separate cookies, localStorage, sessionStorage, IndexedDB and Cache Storage. - Optional matching tab groups and site rules: open in a chosen container, or ask. - Restore container tabs after restart or Reopen closed tab; uncertain assignments wait for your choice. - Reopen remembered tabs after closing a container group. - Export/import your setup; cookies excluded unless you opt in. - Light/dark themes and keyboard-accessible controls. OPTIONAL AI BRIDGE: OFF BY DEFAULT Your own MCP client, such as Claude Code, Codex or Cursor, can use your signed-in tabs. Requires macOS/Linux, Node.js 20+ and a separate open-source companion: npx splitsession-bridge install In Settings > For AI agents, switch on Agent bridge, read the disclosure and choose Allow agent access, then allow Chrome's optional permission. SplitSession restarts itself once and reopens Settings: Connected, if the companion is installed. Switching off disconnects and removes the permission. Containers work without the companion. The agent can list tabs and containers, open pages in a chosen container, navigate and close tabs, read text/HTML and page snapshots, click and type by element, select options, scroll and wait. Screenshots capture only the visible part of the tab on show. The store version has no debugger access. It cannot run agent-supplied JavaScript, send key presses, upload files, or read console output or network logs. Some sites ignore its script-generated clicks or typing. Access includes ordinary and container tabs in every window of a connected profile, including signed-in pages. There are no per-site controls or per-action confirmations. Enable only for programs you trust. Activity indicators are on by default. PRIVACY No SplitSession server, account, analytics or telemetry. Cookies and settings stay locally, without sync or encryption by SplitSession. Bridge data, including tab details, page content and screenshots, passes through native messaging and local Unix sockets to the companion and your agent. There is no network port. SplitSession sends nothing to a server; your agent may send data to its AI provider under its own terms and settings. LIMITS Containers do not hide your IP address or browser fingerprint and are not a security sandbox. Service workers and shared workers are disabled in container tabs. Offline features and push notifications may also be affected in ordinary tabs on sites used by containers. Pages opened outside SplitSession may first load with your regular profile's cookies. Isolation gaps also occur during extension restarts, updates and browser session restore. Prefer opening pages through SplitSession or its site rules. Some sign-in flows may fail. Start Google sign-in from the site inside its container; avoid a rule for Google's sign-in page. PERMISSIONS All-site access lets SplitSession separate cookies and storage wherever you use containers. Other permissions manage tabs, groups, site rules and restore, store your setup locally and remove service workers for isolation. Version 0.2.0 adds no required permissions and causes no update permission prompt. "Communicate with cooperating native applications" is requested only when you enable the optional bridge. Free and open source (MIT). Source and documented limits: https://github.com/Misyuk-T/splitsession Privacy: https://misyuk-t.github.io/splitsession/privacy