Save a site's logins as named profiles and switch between them in one click. Everything stays on your device.
Users
0
store count
Rating
0.0 / 5
unchanged in 30 days
Ratings
0
total ratings
Store rank
#367K
#301K among extensions
Version
0.1.0
updated 20 Nov 2026
Publisher and listing changes
From our daily record of this listing since 20 Nov 2026
No change of publisher name, contact email, website, privacy policy or listing name since 20 Nov 2026.
About Sleight — Session Switcher
Sleight saves the logged-in state of a website as named profiles, for example "Admin" and "Test user", and switches between them in one click. It is for developers and QA testers who check roles and accounts on their own apps, and for anyone with several accounts on one site. You do not need separate browser profiles or incognito windows.
How it works
1. Open a site and log in.
2. Open Sleight and save the current session as a profile.
3. Log in as someone else, or start a blank session, and save that too.
4. Pick a profile in the popup. Sleight saves the current state back into the active profile, clears the site's state locally, restores the profile you chose and reloads the site's open tabs.
What a profile holds
- The site's cookies, including HttpOnly cookies and all their attributes.
- The site's localStorage.
- The site's sessionStorage.
A profile belongs to one site. The site is the whole registrable domain, so example.com and all its subdomains count as one site. One profile is active per site at a time. Whatever happens on the site while a profile is active belongs to that profile. If you sign out and sign in as someone else while "Admin" is active, "Admin" now holds that login.
Sleight never uses a site's own logout. Logging out on the server would end the saved session.
Privacy
- Profiles are stored in your browser's local extension storage, on your device.
- Profiles are not encrypted there. Anyone who can read your browser's data on this device can read them.
- Nothing is sent anywhere. There is no analytics and no crash reporting.
- Sleight asks for access to a site the first time you save a profile there. It does not ask for access to all sites up front.
- Sleight acts on a site only when you start a save, switch, new profile or blank session. It also finishes a switch you started if it was interrupted, for example if the browser closed part-way.
- When you open the popup on a site that has profiles, Sleight reads the site's cookies to tell whether the current session is saved. It does not store them unless you save or switch.
- On sites it has access to, Sleight reads the address of your open tabs to show the active profile on the toolbar badge. The address is not stored or sent anywhere.
- Sleight does not work in incognito windows.
- You can delete one profile, or choose "Delete all data…" on the options page. Removing the extension also removes its data.
Export and import
You can export selected profiles to a file and import them on another device. The file is encrypted with a passphrase you choose (AES-GCM, with a key derived from the passphrase). The file contains live logins. Anyone who has the file and the passphrase can sign in as those accounts. Share it only with people you trust.
Known limitations
- Subdomains with no open tab are not switched. If a switch happens while a subdomain has no open tab, that subdomain's localStorage keeps the previous profile's data.
- Sites that keep their login in IndexedDB (Firebase Auth is a common case) will not switch correctly. Sleight does not save IndexedDB.
- A login that spans several registrable domains, such as Google across google.com and youtube.com, is not covered by one profile.
- Cookies ignore the port. localhost:3000 and localhost:5173 share cookies, while their localStorage is separate.
- Before a switch changes anything, Sleight moves the site's tabs to a waiting page. If a tab cannot be moved within about 10 seconds, for example because a page is slow to respond, the switch stops with a message that tabs could not be moved. Nothing has been changed at that point, and you can retry.
- After the cookies are swapped, Sleight waits for each tab to load again, up to about 40 seconds for a slow page. If a tab has still not loaded by then, the switch finishes without it and the popup says how many tabs could not be updated. Such a tab can keep the previous profile's localStorage beside the new login; switching to another profile and back fixes it.
- A site's own service worker, or the site embedded as a frame on another site, can still write cookies while a switch is in progress.
- sessionStorage is restored only in the tab the switch was started from. It is cleared in the site's other tabs.
Sleight works in Chrome 130 or later and other Chromium-based browsers built on it.
Version history
1 versions recorded
No update since 20 Nov 2026 changed the permissions or site access.