Why an extension stops working
Chrome has removed support for Manifest V2, the older format extensions were built in. An extension that has not been rebuilt for Manifest V3 no longer loads. If SessionBox stopped loading in your copy of Chrome, that change is the likely cause. NVX Session is built on Manifest V3, the current format, so the same change does not affect it.
What NVX Session does
It gives each tab its own session, so you can keep multiple accounts on the same site open in one window: work and personal Google side by side without the /u/0 wrong-account trap, or one site open as admin, user and guest at the same time for testing. Tabs are coloured by session, a link can be opened into a session from the right-click menu, and sessions are unlimited and free.
Where it differs
- How sessions are kept apart
- NVX does not swap cookies in and out of the browser's own store. It rewrites the Cookie header on each request from a session's tabs, so several tabs on the same site can load at once and each one is sent its own session's cookies.
- Where your sessions live
- On your machine only. There are no cloud profiles and no account to sign into. Pro adds optional encrypted sync, which carries a session's name, colour and settings between your devices, never its cookies or logins.
- What is isolated
- Cookies, including ones set by page scripts, plus localStorage and sessionStorage. IndexedDB is detected and named rather than isolated in the free build, and the HTTP cache is shared between sessions because an extension cannot separate it. Both are stated on the Pro page.
- Per-session IP address
- Not offered. Every session uses your normal connection.
- Browsers
- Chrome, Edge, Brave, Vivaldi and Arc, and Opera GX through its own backend.
Moving your accounts over
There is no importer, and NVX does not read another extension's data. Create a session for each account and sign in fresh inside it. You can also copy the browser's current login into a session, but for Google and other single sign-on providers a fresh sign-in inside the session is the reliable path.
Before you rely on it
Read why it asks for each permission and what leaves your machine. The code is open source at github.com/Envxsion/nvx_session.