Tabsona — multi-account tabs & saved logins

Give each tab its own login. Save a set of signed-in sites as a persona and reopen the whole set in one click.

Testing six roles across your own apps means six Chrome profiles, six windows, or six browsers. Tabsona gives each tab its own login instead. A PERSONA is who you are across a set of apps — admin, tenant-A, staging. It holds one saved login per site. Click Open all and the whole scenario opens: three tabs, three apps, the right identity in each, grouped in a Chrome tab group. WHAT IT DOES • Each tab keeps its own cookies and its own page storage • Save a login and reopen it later — sessions outlive their tabs • Open a whole persona in one click • Two accounts on one site, live at the same time • Duplicate a persona, logins included, to spin up another tenant • Every persona opens in its own Chrome tab group, named and coloured after it • Export and import personas SIGN-IN THROUGH OTHER WEBSITES Many apps sign you in through another website (WorkOS, Auth0, Okta, Google). If a persona tab reached one of those with your normal browser login, it would come back signed in as YOU. So a persona tab stops BEFORE it visits a website Tabsona is not allowed on, sends nothing, and asks: Allow and continue, Allow on all sites, or Open in a normal tab. Allow on all sites is one Chrome prompt, asked once and off until you click it. A sign-in chain you have seen is remembered, so one prompt covers it, and a red alert in the popup tells you when a persona is signed in through a website that is not allowed. USE MY NORMAL LOGIN ON CHOSEN WEBSITES Sign in with Google from a persona: add accounts.google.com to a short list in Settings and a persona tab reaches it with your browser's own login, while the app's own login stays separate per persona. Opt-in, nothing is on the list until you add it, and the badge on those pages says so in plain words. WHY IT IS DIFFERENT Most multi-login extensions isolate cookies only, so the moment an app keeps its token in localStorage — which most modern apps do — both tabs show the same user and nothing tells you. Tabsona isolates page storage too, and when it cannot fully isolate a site it SAYS SO on the tab rather than letting you assume. Isolation is not all-or-nothing. A service worker, an IndexedDB token or a cross-origin frame can defeat it on a given site. Tabsona measures what it actually achieved per site and shows it, because a tool that looks isolated while leaking is worse than no tool. WHAT IT IS NOT This is a developer tool for testing your own applications. It does not spoof your browser fingerprint, does not route traffic through proxies, and is not built for evading bans or platform rules. Every persona shares your real browser fingerprint. PRIVACY Everything stays on your machine in local extension storage. No server, no account, no telemetry, nothing is uploaded. Site access is granted by you, through Chrome's own permission prompt: one website at a time, or every website once with Allow on all sites. Nothing is granted until you click. Open source: https://github.com/khanakia/tabsona