Capture Complete Login States
Save cookies, localStorage, and sessionStorage together—then restore the state with its original domain context.
Capture complete login states, switch between accounts in seconds, protect TOTP secrets, and restore everything without surrendering your data to a cloud service.
Complete Session Control
SesWi treats a login state as a complete system: cookies, browser storage, domain context, timestamps, encryption, and the 2FA credentials that keep the account usable.
Save cookies, localStorage, and sessionStorage together—then restore the state with its original domain context.
Store, scan, and generate rotating 2FA codes without leaving the extension.
Review and restore JSON, Netscape, Cookie Editor, Cookie header, key-value text, and encrypted OWI files.
Clean cookies, storage, history, and cache—or export current-tab data without saving a permanent session.
Browser Commands
Open SesWi from anywhere, then use Current Tab tools for deliberate site-data and window cleanup.
Bring the popup into focus from any normal browser tab.
Use the Window tab in Clean Current Tab to close every other tab in the current window while keeping the active tab open.
Local-First Security
Master Password protection, authenticated encryption, and an extension-memory unlock cache protect sensitive data without turning SesWi into another cloud account.
Build & Install
SesWi is open source. Build the target for your browser, then load the generated folder as an unpacked or temporary extension.
Open chrome://extensions, enable Developer mode, then choose “Load unpacked.”
Open about:debugging and load the generated manifest as a temporary add-on.
Questions
The important details, without hiding behind marketing language.
No. The current architecture is local-first. Cloud backup is a future roadmap item, not a hidden dependency.
A complete session can include cookies, localStorage, sessionStorage, original URL/domain metadata, and timestamp/index metadata.
No. JSON, Netscape, and Cookie Editor formats are readable raw formats. Use OWI when you need an encrypted backup.
Most cookie and storage-based sessions work, but complex SSO or device-bound authentication may still require refresh or manual verification.
Build SesWi, inspect the source, and turn account switching from repetitive work into a deliberate command.
View Source on GitHub ↗