How to Set Up Browser Proxy Extensions for Chrome and Edge: Complete Guide

The fanqiang repository provides one-click browser proxy extensions called ChromeGo and EdgeGo that bundle multiple proxy protocols and automatically configure Chrome or Edge to bypass censorship without system-wide changes.

The bannedbook/fanqiang repository is a comprehensive censorship circumvention toolkit that distributes ready-to-use browser proxy extensions for Google Chrome and Microsoft Edge. These self-contained packages eliminate the need for system-level VPN installations by embedding proxy clients directly into portable browser launchers. This guide explains how to set up browser proxy extensions for Chrome and Edge using the official ChromeGo and EdgeGo distributions.

What Are ChromeGo and EdgeGo?

ChromeGo and EdgeGo are dedicated browser proxy packages maintained in the bannedbook/fanqiang repository. ChromeGo targets Google Chrome specifically, while EdgeGo provides identical functionality for Microsoft Edge users. Both extensions package ten distinct proxy channels—including Clash, Xray, v2go, hysteria, sing-box, naiveproxy, and psiphon—into a single downloadable archive that automatically selects the fastest available node.

According to ChromeGo/README.md and EdgeGo/README.md, these tools function as self-contained environments that do not modify system network settings. This architecture makes them ideal for temporary use cases or environments where users cannot install system-level VPN clients.

How the Browser Proxy Architecture Works

Bundled Binaries and Protocols

Each archive contains pre-compiled binaries for multiple proxy protocols located in the extracted folder structure. As implemented in the repository source, these include executables for Clash, Xray, v2go, hysteria, sing-box, naiveproxy, and psiphon.

Proxy Selection and Launcher

A proxy selector script detects the fastest reachable server from the pre-loaded free node list. The launcher then modifies the browser's command-line arguments—typically using --proxy-server= or injecting a local PAC file—to route traffic through the selected proxy endpoint.

Self-Update Mechanism

The packages include a self-update mechanism that periodically fetches fresh node lists from remote sources to maintain connection reliability without manual intervention.

Installing ChromeGo: Chrome Proxy Extension Setup

Follow these steps documented in ChromeGo/README.md to configure the Chrome proxy extension:

1. Download the latest ChromeGo.7z archive from one of four official mirrors:

   • https://d1a.mygrok.top/ChromeGo.7z
   • https://d1.mygrok.top/ChromeGo.7z
   • https://d2.mygrok.top/ChromeGo.7z
   • https://github.com/bannedbook/fanqiang/releases

2. Extract the .7z file to a folder path containing no spaces or Chinese characters.

3. Open the extracted folder and read the "使用说明（必看）" document for first-time configuration requirements.

4. Execute the launch script (ChromeGo.exe). The script automatically starts Google Chrome with the appropriate proxy settings applied.

# Example: Running ChromeGo on Windows

ChromeGo.exe

# Chrome launches with automatic proxy selection enabled

Installing EdgeGo: Edge Proxy Extension Setup

According to EdgeGo/README.md in the repository, configure the Edge proxy extension using these steps:

1. Download the EdgeGo package from the repository releases or clone the EdgeGo folder.

2. Extract the archive to a path without spaces or non-ASCII characters to prevent execution errors.

3. Review the "使用说明（必看）" file for initial configuration and usage notes.

4. Run the provided launch executable. Microsoft Edge will open with the active proxy configuration automatically applied.

Manual Configuration and Advanced Usage

For users who prefer specific protocols over automatic selection, the bundled binaries support manual invocation. As implemented in the bannedbook/fanqiang source structure, you can run individual proxy clients and point your browser to them directly.

Example using the Clash binary:

# Run the built-in Clash client on port 7890

./clash-linux-amd64 -c ./config.yaml

# Then start Chrome with a PAC file pointing to the local proxy

chrome --proxy-pac-url=http://127.0.0.1:7890/pac.js

This method bypasses the automatic selector while maintaining access to the pre-configured node lists located in the extracted folder.

Key Documentation Files

The following files in the repository provide authoritative configuration details:

• ChromeGo/README.md: Contains download mirrors, extraction requirements, and troubleshooting for the Chrome proxy bundle.
• EdgeGo/README.md: Documents the Edge-specific implementation, including launcher behavior and update mechanisms.
• ChromeGoMac/README.md: macOS equivalent of the ChromeGo package.
• README.md (root): Central hub listing all platforms, tutorials, and alternative download links.
• v2ss/自建V2ray服务器简明教程.md: Guide for building personal V2Ray servers when bundled free nodes are unavailable.
• v2ss/自建Shadowsocks服务器简明教程.md: Instructions for Shadowsocks server deployment as an alternative proxy method.

Summary

• ChromeGo and EdgeGo are self-contained browser proxy extensions from the bannedbook/fanqiang repository that require no system-wide installation.
• Both packages bundle ten proxy protocols (Clash, Xray, hysteria, etc.) and automatically select the fastest node via the proxy selector script.
• Installation requires extracting the .7z archive to a path without spaces or Chinese characters, then running the launch executable (ChromeGo.exe or equivalent).
• The launcher modifies Chrome or Edge command-line arguments (e.g., --proxy-server= or --proxy-pac-url=) to apply proxy settings without changing system network configuration.
• Advanced users can manually invoke specific binaries like clash-linux-amd64 on port 7890 and configure browsers to use http://127.0.0.1:7890/pac.js.

Frequently Asked Questions

Do ChromeGo and EdgeGo require administrator privileges?

No. Because these browser proxy extensions operate as portable applications that modify only the browser instance's command-line arguments, they do not require system-level installation or administrator rights. The proxy configuration applies only to the launched Chrome or Edge process, leaving system network settings untouched.

Can I use these extensions on macOS?

Yes. The repository maintains ChromeGoMac/README.md, which documents a macOS-specific version of the ChromeGo package. The architecture remains identical—bundled binaries with automatic proxy selection—but adapted for macOS directory structures and Chrome installation paths.

What should I do if the bundled free nodes stop working?

If the pre-configured free servers become unavailable, refer to v2ss/自建V2ray服务器简明教程.md or v2ss/自建Shadowsocks服务器简明教程.md in the repository. These files provide step-by-step instructions for building personal V2Ray or Shadowsocks servers that can replace the default node lists in your local configuration.

Why must the extraction path avoid spaces and Chinese characters?

The launcher scripts and bundled proxy binaries rely on command-line execution and file path resolution that may fail with spaces or non-ASCII characters in the directory path. Extracting to a simple path like C:\ChromeGo\ ensures the ChromeGo.exe launcher and protocol selectors function correctly when spawning subprocesses and resolving relative configuration paths.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}