What problem does this solve? (describe the problem you're experiencing)
Currently, setting up a proxy applies globally to the entire browser instance or session, making it impossible to route traffic on a per-tab basis.
When managing multiple tasks, testing local/regional environments, or conducting network debugging, I often need different tabs to route through different proxy servers simultaneously. Switcher extensions or global settings require constant toggling, which disrupts the workflow and risks mixing up environment states.
How are you working around this today? (your current solution or workaround)
Running multiple separate browser profiles or opening multiple distinct browser instances simultaneously, each configured with a different global proxy.
Using third-party extension proxies, which are often limited by standard browser extension APIs and cannot fully isolate socket connections or handle low-level network proxy configurations per tab cleanly.
What's your proposed solution? (how should BrowserOS address this?)
Per-Tab / Contextual Proxy Assignment: Allow users to specify a proxy rule (HTTP/HTTPS/SOCKS5) when creating or opening a new tab.
UI/UX Integration: Provide an option in the tab context menu (e.g., Right Click Tab / New Tab -> Open with Proxy...) or via a dedicated API/command palette to attach a proxy profile to a specific tab.
Visual Indicator: Display a small badge or icon on the tab header indicating that a specific proxy is active for that context.
Additional context (optional - add screenshots, examples, or other helpful details)
This feature would significantly benefit developers, testers, and power users who work with multi-region web applications, web scrapers, advertising verification tools, or localized content debugging.
Standard browsers (like Chrome/Firefox) struggle with native per-tab proxying without complex extension workarounds, making this a major potential differentiator for BrowserOS.
What problem does this solve? (describe the problem you're experiencing)
Currently, setting up a proxy applies globally to the entire browser instance or session, making it impossible to route traffic on a per-tab basis.
When managing multiple tasks, testing local/regional environments, or conducting network debugging, I often need different tabs to route through different proxy servers simultaneously. Switcher extensions or global settings require constant toggling, which disrupts the workflow and risks mixing up environment states.
How are you working around this today? (your current solution or workaround)
Running multiple separate browser profiles or opening multiple distinct browser instances simultaneously, each configured with a different global proxy.
Using third-party extension proxies, which are often limited by standard browser extension APIs and cannot fully isolate socket connections or handle low-level network proxy configurations per tab cleanly.
What's your proposed solution? (how should BrowserOS address this?)
Per-Tab / Contextual Proxy Assignment: Allow users to specify a proxy rule (HTTP/HTTPS/SOCKS5) when creating or opening a new tab.
UI/UX Integration: Provide an option in the tab context menu (e.g., Right Click Tab / New Tab -> Open with Proxy...) or via a dedicated API/command palette to attach a proxy profile to a specific tab.
Visual Indicator: Display a small badge or icon on the tab header indicating that a specific proxy is active for that context.
Additional context (optional - add screenshots, examples, or other helpful details)
This feature would significantly benefit developers, testers, and power users who work with multi-region web applications, web scrapers, advertising verification tools, or localized content debugging.
Standard browsers (like Chrome/Firefox) struggle with native per-tab proxying without complex extension workarounds, making this a major potential differentiator for BrowserOS.