TabGroup Proxy

Bind a proxy server to a Chrome tab group. All tabs in the group route through the proxy automatically — no URL rules.

TabGroup Proxy is a Chrome extension that binds a proxy server to a Chrome tab group and remembers which domains belong on it. Open a site once inside a proxy-bound group, and it keeps using that proxy even when reopened later in a tab outside any group. New domains default to a direct connection. No URL rules, no domain lists, no global switch. ▌ What problem does TabGroup Proxy solve? You already organize work in Chrome tab groups. One group holds foreign sites that need a proxy, another holds work, another holds personal browsing. Existing proxy extensions don't understand tab groups — they either flip a global switch or ask you to maintain a hand-curated list of domains. TabGroup Proxy uses your existing tab groups as the source of truth: assign a proxy to a group once, and every tab inside that group routes through it automatically. ▌ How does TabGroup Proxy compare to other Chrome proxy extensions? • TabGroup Proxy — per Chrome tab group + sticky domain memory. Learns from your behavior. Yes. • FoxyProxy — URL pattern rules only. No tab group binding. No learning. • Proxy SwitchyOmega / ZeroOmega — global switch + URL rules. No tab group binding. No learning. • TabProxy — per-tab manual. No tab group binding. No learning. • Proxy Switcher and Manager — global switch. No tab group binding. No learning. • Web Proxy Per Tab — per-tab manual. No tab group binding. No learning. TabGroup Proxy is the only extension that uses native Chrome tab groups as the binding unit and grows its domain map automatically from your browsing. ▌ How does it work? Add your proxy in Settings — HTTP, HTTPS, or SOCKS5. DIRECT is built-in; no setup needed. Open Settings — every Chrome tab group in the current window is listed. Pick a proxy from the dropdown next to a group. Done. The extension watches your tab groups in real time, builds a domain → proxy map (persisted in chrome.storage.local), and feeds it to Chrome via a PAC script. The map grows whenever you visit a new site inside a proxy-bound group. Visit that site later in any tab — even outside the group — and it keeps using the same proxy. The memorized list is fully visible and clearable in Settings. ▌ Features • Bind a proxy to any Chrome tab group — one dropdown, no URL patterns. • Sticky domain memory — domains opened inside a proxy-bound group keep using that proxy forever, even outside the group. Reviewable and clearable. • Per-tab manual override via the popup for one-off exceptions. • Built-in DIRECT profile — no manual "no proxy" entry needed. • Supports HTTP, HTTPS, SOCKS5. • Built-in authentication for HTTP/HTTPS proxies — no system password dialog on every tab. • Color-coded badge: group color for group-routed tabs, cyan for memorized domains, purple for manual overrides. • Survives Chrome restart: bindings are restored by tab group title and color. • Yandex Browser fallback: when tab groups aren't exposed by the browser, bind a proxy to a whole window instead. • Anonymous, aggregated usage statistics — only bucketed counts (e.g. "2-3 profiles", "6-15 tabs"). No URLs, no domains, no proxy hosts, no credentials. IP discarded server-side. • Open source. ▌ Routing priority When picking a proxy for a request, TabGroup Proxy checks in order: (1) per-tab override, (2) the tab's current group binding, (3) per-window binding (Yandex fallback), (4) sticky domain memory, (5) DIRECT. ▌ Known limitations • Chrome does not support SOCKS5 with username/password at the browser level. If your SOCKS5 needs auth, run a local tunnel (e.g. ssh -D 1080 user@server) and point the extension at localhost:1080. • Proxy applies only to new requests. After changing a binding, reload the tab — the popup has a Reload button. • Domain matching is at the registrable-domain level (eTLD+1). All of *.example.com goes through the same proxy. Cross-domain subresources from unrelated CDNs go direct — a well-known PAC limitation shared by FoxyProxy and ZeroOmega. ▌ Privacy Proxy credentials, tab metadata, group bindings, and the domain memory all live in your local Chrome profile and never leave it. The only proxied network connections the extension causes are to the proxy server you configured yourself. ▌ Frequently asked questions Q: Does it work in Yandex Browser? A: Partially. Yandex Browser does not expose Chrome's tab groups API, so group binding is unavailable. As a workaround, TabGroup Proxy detects Yandex and lets you bind a proxy to a whole window. Per-tab override and sticky memory work normally. Q: Does it support SOCKS5 with username/password? A: Not directly — Chrome itself does not. Run a local tunnel and point the extension at localhost. Q: Where are my proxy credentials stored? A: In chrome.storage.local, on your machine only. Other extensions and websites cannot read it. Q: Does it work across Chrome restarts? A: Yes. Group bindings are restored by title + color of each tab group. Q: Is it open source? A: Yes.