Browser Multi-Account Switcher v1.1 Adds Auto-Logout

Open-Source Extension Solves Multi-Account Browser Headaches

A developer-built browser extension called Multi Accounts Switch has released version 1.1 with a critical new feature: automatic logout functionality that clears all login states before switching to a new account. The update addresses a longstanding frustration for power users who juggle multiple accounts across platforms like Google, GitHub, AWS consoles, and social media — without resorting to clunky workarounds like multiple browser profiles or incognito windows.

The extension, available on the Microsoft Edge Add-ons Store and other Chromium-based browsers, is fully open source on GitHub. Its creator says the update now covers 99% of real-world multi-account switching scenarios.

Key Takeaways at a Glance

• Auto-logout added: v1.1 clears all login cookies and session data under the current domain before switching accounts
• Non-destructive logout: The feature logs users out without deleting or deactivating accounts — it is a session clear, not an account cancellation
• 99% coverage: The developer claims the new approach handles virtually all common multi-account switching scenarios
• Edge-first availability: Direct installation is available from the Microsoft Edge Add-ons Store, with manual downloads for Chrome and other browsers
• Fully open source: The complete source code is published on GitHub under the repository 'JiaMuQing/mulit_accounts_switch'
• Community-driven: The v1.1 improvements were directly inspired by user feedback from the v1.0 release

The Problem: Incomplete Account Switching Was Breaking Workflows

Anyone who manages multiple accounts on the same platform understands the pain. You log into Account A on a website, then try to switch to Account B — but the browser still holds residual session tokens, cookies, or cached credentials from Account A. The result is unpredictable behavior: mixed account states, permission errors, or simply landing back on Account A's dashboard despite attempting to switch.

Before v1.1, the Multi Accounts Switch extension handled the login injection for new accounts but did not automatically clear the previous account's session data. Users reported that this led to 'incomplete switching,' where traces of the old session interfered with the new login. It was functional but unreliable in edge cases.

Traditional workarounds for this problem include maintaining separate browser profiles (Chrome supports this natively, as does Edge and Firefox), using incognito or private windows, or relying on enterprise tools like Google Workspace's account picker. However, each of these solutions has drawbacks — browser profiles consume significant memory, incognito windows don't persist useful extensions, and platform-native account pickers only work within their own ecosystem.

How the v1.1 Update Works Under the Hood

The core improvement in version 1.1 is straightforward but effective. When a user triggers an account switch, the extension now performs a 2-step process:

1. Session cleanup: It identifies and clears all login-related data (cookies, local storage tokens, session storage) associated with the current domain
2. Fresh login: Only after the cleanup is complete does the extension inject the new account's credentials and initiate the login flow

This approach ensures a clean slate for every switch, eliminating the residual session conflicts that plagued the previous version. The developer describes this as a 'non-official logout' — meaning it mimics the effect of clicking a site's logout button by clearing browser-side session data, without actually hitting the platform's server-side logout API endpoint.

The distinction matters. A server-side logout might revoke refresh tokens, invalidate sessions across devices, or trigger security notifications. The extension's approach is lighter: it only clears the local browser's knowledge of the session, leaving the server-side session intact. This means you can switch back to a previous account without needing to re-authenticate from scratch in many cases.

Installation and Browser Compatibility

The extension is currently optimized for Chromium-based browsers, which dominate the global browser market with over 65% share according to StatCounter data. Here is how to get started:

• Microsoft Edge: Install directly from the Edge Add-ons Store — no sideloading required
• Google Chrome: Download the extension package from the developer's product page and load it manually via Chrome's developer mode
• Other Chromium browsers (Brave, Vivaldi, Opera): Same manual installation process as Chrome
• Firefox and Safari: Not currently supported, as the extension relies on Chromium-specific APIs

The developer's product page at product.xyptkd.cn provides download links for non-Edge browsers. The installation process for manual loading involves enabling developer mode in your browser's extensions settings, then dragging and dropping the .crx or unpacked extension folder.

Why This Matters for Developers and Power Users

Multi-account management is not a niche concern. It is a daily reality for several large user segments:

• Freelancers and agencies who manage client accounts across platforms like Google Ads, Facebook Business Manager, or AWS
• Developers who maintain separate GitHub, GitLab, or cloud console accounts for personal and work projects
• QA testers who need to verify application behavior across different user roles and permission levels
• Social media managers who operate multiple brand accounts on platforms like Twitter/X, Instagram, or LinkedIn
• Security researchers who maintain isolated identities for different testing environments

For these users, the overhead of managing multiple browser profiles or constantly clearing cookies manually represents real productivity loss. A lightweight extension that automates this process — especially one that is open source and auditable — fills a genuine gap in the browser productivity tool ecosystem.

Compared to commercial alternatives like SessionBox or Multilogin, which can cost $20-$100+ per month and target enterprise anti-detection use cases, Multi Accounts Switch positions itself as a free, transparent, and simpler solution for everyday account switching needs.

Open Source Transparency Builds Trust

One of the extension's strongest selling points is its fully open-source codebase, hosted on GitHub at JiaMuQing/mulit_accounts_switch. The developer describes it as a 'small toy project' — a modest characterization that actually works in its favor.

Browser extensions that handle authentication data occupy a uniquely sensitive position. They have access to cookies, session tokens, and potentially stored credentials. Users rightfully worry about extensions that could exfiltrate this data. An open-source codebase allows security-conscious users and independent researchers to audit exactly what the extension does with their data.

The project's GitHub repository also serves as a feedback channel. The developer credits community suggestions from the v1.0 release as the driving force behind the v1.1 improvements. This iterative, community-responsive development model is a hallmark of healthy open-source projects, even small ones.

Limitations and Considerations

While the v1.1 update represents a significant improvement, users should be aware of several caveats:

• Not a privacy tool: This extension is designed for convenience, not anonymity. It does not spoof fingerprints, rotate IP addresses, or provide the anti-detection features found in tools like Multilogin or GoLogin
• Domain-level clearing: The session cleanup operates at the domain level, which means it will clear all cookies for that domain — not just the ones related to the specific account being switched
• Platform-specific quirks: Some platforms use complex authentication flows (OAuth redirects, multi-domain cookies, iframe-based sessions) that may not be fully covered by the extension's cleanup logic
• Manual credential storage: Users need to configure their account credentials within the extension, which introduces a local security consideration — anyone with physical access to the browser could potentially access stored accounts

The developer acknowledges that the solution covers '99% of use cases,' implicitly recognizing that edge cases exist. For high-security or enterprise environments, dedicated identity management solutions remain the appropriate choice.

Looking Ahead: What Could Come Next

The rapid iteration from v1.0 to v1.1, driven by community feedback, suggests the project has momentum. Several natural next steps could further enhance the extension's utility:

First, encrypted credential storage would address the security concern of locally stored account data. Browser extensions can leverage the Web Crypto API or integrate with system-level credential managers to protect sensitive information at rest.

Second, profile grouping — allowing users to organize accounts by client, project, or platform — would improve the experience for users managing large numbers of accounts. A tagging or folder system within the extension's popup UI could make navigation significantly faster.

Third, cross-browser sync capabilities would let users maintain their account configurations across devices. This is technically challenging for a small open-source project but would dramatically increase the extension's value proposition for professional users.

Finally, a Chrome Web Store listing would remove the friction of manual installation for the browser's largest user base. While the Edge Add-ons Store listing provides a streamlined experience for Edge users, Chrome's market share means that most potential users currently face a more complex setup process.

For now, Multi Accounts Switch v1.1 represents a practical, no-cost solution to a real productivity problem. Its open-source nature, responsive development, and focused feature set make it worth watching — especially for developers and power users tired of the browser profile juggling act.