A fast, minimal proxy switcher for Chromium browsers.
One-click switching, rule-based auto routing, zero frameworks, Manifest V3.
Chrome Web Store · Releases · Rules reference · Architecture · Development
Sockitt manages your proxies - SOCKS5, SOCKS4, HTTP, and HTTPS - and decides, per request, whether traffic goes direct or through one. It is a ground-up, modern take on the classic proxy-switcher extension: no frameworks, a minimal default permission set, and a rule engine that compiles to an optimised PAC script.
Popup: switch profiles on the left; on the right, where this tab routes, its rule, and where it exits
Options: an ordered, first-match-wins rule table, compiled to a PAC script
- Proxy profiles. SOCKS5, SOCKS4, HTTP, or HTTPS servers with a host, port, and per-profile bypass list, plus optional username/password authentication for HTTP(S) proxies. Each profile has an identity: an initials avatar in a colour of your choice, drawn onto the toolbar icon while it is active.
- Built-in modes. Direct (no proxy) and System (use the OS proxy settings).
- Auto Switch profiles. An ordered, first-match-wins rule table. Route by
host wildcard (
*.example.com), host regex, URL wildcard, URL regex, URL keyword, IPv4 CIDR (10.0.0.0/8), host-label count, weekday, or time of day. Rules can target a proxy, Direct, another switch profile, a rule list, or an alias. - Rule lists. Subscribe to AutoProxy/GFWList or plain domain lists by URL with auto-update, or paste one in. Domain entries compile to a single dictionary lookup, so even very large lists stay fast.
- Aliases. Pointer profiles: aim many rules at one alias, then retarget them all by editing the alias once.
- Popup switcher. Change profile in one click, see where the current tab routes, retarget or delete the matching rule inline, or set a temporary per-site override that lasts only until the browser restarts. An optional exit-IP line (off by default) shows where the current tab actually exits — flag, IP, and latency, with the country named in the tooltip.
- Route inspector. Trace any URL through your configuration with the same resolver real routing uses — which rule fired, the chain it walked, where it landed.
- Connection tests. One click routes briefly through a proxy, measures the exit IP/country/latency (auth included), and restores your configuration. Like the exit-IP line, this uses the opt-in IP address lookups (off by default).
- Incognito routing. Optionally give incognito windows their own profile (needs "Allow in Incognito").
- Quick switch. Cycle a chosen set of profiles from the toolbar button or a keyboard shortcut, without opening the popup.
- Sync and control. Optional configuration sync across machines via your browser account, a startup profile, and a guard that re-takes proxy control if another extension grabs it.
- Honest failure states. When a proxy is down, requests fail closed rather
than silently leaking direct. A red mark on the toolbar icon says so — with a
count (
!,!4,!9+) once the failure repeats — and a Proxy errors page names the error, explains it, says which proxy was carrying traffic, and keeps a log. The mark clears itself after 30 seconds without a new failure, because a proxy coming back is something the browser never announces.
From the Chrome Web Store (easiest). Sockitt — Proxy Switcher — one click, and it updates itself.
From a release. Download sockitt.zip from the
latest release and unzip
it. Open chrome://extensions, enable Developer mode, click Load
unpacked, and select the unzipped folder. Useful for trying a version before
it reaches the store, or for pinning one — unpacked installs do not auto-update.
From source.
git clone https://github.com/ptmplop/Sockitt
cd Sockitt
npm install
npm run buildThen load the dist/ folder unpacked as above. Works on Chrome, Edge, Brave,
Opera, Vivaldi, and other Chromium browsers (Chrome 110+).
- Click the Sockitt icon, then Manage profiles & rules > Create >
Proxy. Pick the protocol
and enter the host and port - for example a SOCKS5
ssh -D 1080 myservertunnel on127.0.0.1:1080, or an HTTP proxy with a username and password. - Pick the profile in the popup. Everything now routes through it.
- For per-site routing, create an Auto Switch profile and activate it. As you browse, the popup shows where the current tab routes and lets you add or edit a rule for it - permanently, or as a temporary override. This works while a page is still loading too: a site you cannot reach directly is shown as the tab's target the moment it starts loading, so you can route it through a proxy and have Sockitt request it again, instead of waiting for it to time out.
See docs/rules.md for the full pattern syntax and docs/architecture.md for how it works internally.
By default Sockitt requests four permissions - proxy, storage, activeTab,
and alarms - and no host permissions. It cannot read your browsing
history, does not touch page content, and contains no analytics of any kind.
By default the only network requests it makes are fetches of rule-list URLs that
you configure; enabling IP address lookups (opt-in, below) adds lookups of
ipconfig.is.
Extra capabilities are strictly opt-in and requested only when you use them:
- Per-tab route badge requests
tabs. - HTTP/HTTPS proxy authentication requests
webRequest,webRequestAuthProvider, and all-sites access, which Chromium needs to answer proxy auth challenges. Sockitt asks when you set credentials. - IP address lookups - the popup's exit-IP line and connection tests -
request access to
ipconfig.is, the IP-echo service they query. Off by default; enable them with one setting, which asks for access the first time. - Sync stores your configuration in your own browser account
(
chrome.storage.sync). Proxy credentials are never synced; enter them on each machine.
The proxy error log lives in chrome.storage.session alone: it is gone when the
browser restarts, is never written to your saved configuration, and is never
synced. It records proxy addresses and ports, never credentials.
- No SOCKS authentication. This is a Chromium limitation, not a Sockitt
choice; secure SOCKS proxies with an IP allow-list or a local tunnel
(
ssh -D, WireGuard, and so on). HTTP and HTTPS proxies support username/password auth. - IPv4-only CIDR. CIDR rules match literal IPv4 hosts. Sockitt never resolves DNS in the request path, and IPv6 CIDR is not supported.
- Chromium-family browsers only.
npm install
npm run typecheck # strict TypeScript, no emit
npm test # runs generated PAC scripts in a Node VM
npm run build # production build to dist/
npm run watch # dev build with inline sourcemaps
npm run zip # store-ready sockitt.zip
npm run crx # signed sockitt.crx for Chrome Web Store uploads
npm run shots # regenerate the README + store screenshots from the built UI
npm run icons # regenerate icons from img/logo-source.png (needs ImageMagick)Project layout and design notes are in docs/development.md.
Sockitt is an independent, from-scratch implementation. Its concepts - proxy profiles, PAC-based automatic switching, and the AutoProxy rule-list format - are informed by Proxy SwitchyOmega and its Manifest V3 fork ZeroOmega, which were studied as a reference while designing this extension. Sockitt shares no code with those projects and is released under the MIT license. Thanks to their authors and maintainers for the prior art.
Sockitt has no analytics and no tracking. With IP address lookups off (the
default) it contacts no developer-operated server at all; turning them on adds
lookups of ipconfig.is — the developer's own IP-echo service — which sees only
your connecting IP, never your configuration or browsing. Your configuration
stays on your device (or your own browser account if you enable Sync). See the
full Privacy Policy.