chrome.proxy API
Connect writes a fixed_servers config through Chrome's official proxy API. Disconnect calls settings.clear, so the previous layer — system, PAC, or direct — comes back untouched.
How it works
From download to connected in four steps
No dashboards, no vendor lock-in. IsabiProxy drives Chrome's own proxy settings with one switch.
- 01
Download and load it
Get the zip, unpack it, and load the folder in Chrome via chrome://extensions → Developer mode → Load unpacked. Under a minute, no account.
- 02
Enter your proxy
Type the host and port, pick HTTP, HTTPS, SOCKS4, or SOCKS5, and optionally add a username and password. Everything is validated before it is applied.
- 03
Press Connect
The extension writes Chrome's fixed-servers proxy config. Chrome immediately routes traffic through your server. Status flips to green and the form locks.
- 04
Press Disconnect
The extension clears its config, and Chrome falls back to whatever it used before — system proxy, PAC script, or direct. Your previous setup is never destroyed.
Under the hood
Automatic proxy login
For HTTP and HTTPS proxies, the service worker answers Proxy-Authenticate challenges via webRequestAuthProvider, so you are not re-typing your password on every page.
Protocol handling
Scheme is mapped per protocol. SOCKS4 and SOCKS5 cannot carry credentials in Chromium — the extension warns you clearly instead of pretending.
Persistent state
Your on/off choice and settings are remembered per browser profile. Restart Chrome and the proxy returns exactly the way you left it.
Have a proxy ready to test?
The demo page shows the real popup UI in action.