How to Use the ChromeGo Browser Extension for VPN: Complete Setup Guide

The ChromeGo browser extension for VPN is a Windows-based meta-package bundled with 10 proxy channels (Clash, Xray, V2Ray, Hysteria, Sing-Box, and others) that launches via simple bash scripts after extraction from a 7z archive.

The ChromeGo package from the bannedbook/fanqiang repository provides one of the fastest ways to establish a VPN connection on Windows without manual configuration. Unlike traditional browser extensions, ChromeGo operates as a standalone proxy launcher that works with Chrome, Edge, or any application that supports SOCKS5/HTTP proxy settings. The package contains pre-configured free servers and automated scripts that eliminate the need to edit JSON or YAML configuration files by hand.

What Is ChromeGo and How It Works

ChromeGo is a meta-package design built around a compressed 7z archive. According to the source code at [ChromeGo/README.md](https://github.com/bannedbook/fanqiang/blob/master/ChromeGo/README.md), the archive contains:

• Binary executables for 10 different proxy clients (Clash Meta, Xray, V2Ray, Hysteria2, Sing-Box, NaïveProxy, Psiphon, Brook, Shadowsocks, SSR, Trojan)
• Pre-written configuration files pointing to a rotating pool of free servers
• Shell launch scripts (*.sh) that start the selected client with the correct configuration

The architecture delegates protocol selection to the user through numbered scripts rather than a graphical interface. This design keeps the package lightweight and avoids dependencies on .NET or other runtime frameworks.

Downloading and Extracting ChromeGo

Step 1: Obtain the Archive

Download the latest release from the [ChromeGo/README.md](https://github.com/bannedbook/fanqiang/blob/master/ChromeGo/README.md) page. The file is distributed as a password-protected 7z archive with the password jww.

Step 2: Extract with Proper Path Handling

Critical requirement from the source documentation: the extraction path must contain no Chinese characters or spaces.

Correct extraction paths:

• C:\Tools\ChromeGo
• %USERPROFILE%\Downloads\ChromeGo

Incorrect paths (will cause script failures):

• C:\用户\下载\ChromeGo
• C:\Program Files\Chrome Go

Use 7-Zip for extraction—Windows Explorer's built-in extractor may mishandle the archive structure.

Launching the ChromeGo VPN

After extraction, navigate to the folder and execute the appropriate launch script.

Start Clash Meta (Recommended Default)

cd %USERPROFILE%\Downloads\ChromeGo
bash clash.meta.sh

The clash.meta.sh script launches clash-meta.exe with a bundled configuration that automatically selects the fastest available node from the free server pool. Clash Meta provides the most mature rule-based routing and is the default recommendation in [ChromeGo/README.md](https://github.com/bannedbook/fanqiang/blob/master/ChromeGo/README.md).

Alternative Channels (Manual Selection)

ChromeGo provides numbered scripts for each protocol:

Script	Protocol	Use Case
bash start_0.sh	Clash	Rule-based automatic routing
bash start_1.sh	Xray	Modern VMess/VLESS/Trojan
bash start_2.sh	V2Ray	Classic V2Ray core
bash start_3.sh	V2Go	Lightweight V2Ray variant
bash start_4.sh	Hysteria2	UDP-based low-latency gaming
bash start_5.sh	Sing-Box	Multi-protocol unified client
bash start_6.sh	NaïveProxy	TLS-obfuscated HTTP proxy
bash start_7.sh	Psiphon	Domain-fronted anti-censorship
bash start_8.sh	Brook	Simple SOCKS5 proxy
bash start_9.sh	Quick/SSR	Legacy ShadowsocksR support

Example switching to Hysteria2 for low-latency applications:

cd %USERPROFILE%\Downloads\ChromeGo
bash start_4.sh

Configuring Chrome to Use ChromeGo

Once a proxy client is running, configure Chrome to route traffic through it.

Method 1: System Proxy (Simplest)

Most ChromeGo scripts automatically set the system proxy to 127.0.0.1:7890 (Clash default) or protocol-specific ports. Chrome respects system proxy settings by default—no browser configuration needed.

Verify the proxy is active by checking your IP address in Chrome.

Method 2: Chrome Command-Line Flag

Launch Chrome with explicit proxy settings:

"C:\Program Files\Google\Chrome\Application\chrome.exe" --proxy-server="socks5://127.0.0.1:7890"

Replace 7890 with the actual port shown in the script's console output (Hysteria2 uses 1080, V2Ray uses 1090, etc.).

Method 3: Extension-Based Proxy Switching

Install the Proxy SwitchyOmega extension in Chrome, then configure:

Protocol: SOCKS5
Server: 127.0.0.1
Port: 7890  (or as shown in script output)

This method allows quick toggling between direct and proxied connections without restarting Chrome.

macOS Equivalent: ChromeGoMac

For macOS users, the repository provides ChromeGoMac with identical architecture:

cd ~/Downloads/ChromeGoMac
bash clash.meta.sh

The macOS package uses the same bash script pattern but bundles Darwin-compiled binaries. The clash.meta.sh script in ChromeGoMac is specifically tuned for macOS network interfaces.

Troubleshooting Common Issues

Script Fails with "bash: command not found"

Install Git for Windows, which includes Git Bash. The .sh scripts require a POSIX-compatible shell—Command Prompt and PowerShell cannot execute them directly.

"Cannot find configuration file" Errors

This occurs when the extraction path contains Chinese characters or spaces. Re-extract to C:\ChromeGo or similar.

Antivirus Interference

The [ChromeGo/README.md](https://github.com/bannedbook/fanqiang/blob/master/ChromeGo/README.md) explicitly warns: disable Chinese antivirus software (360, Tencent, etc.) before extraction. These programs frequently quarantine proxy binaries as "suspicious." Windows Defender generally does not interfere.

Port Conflicts

If clash.meta.sh reports "address already in use," another ChromeGo instance or proxy application is running. Kill existing processes or specify alternate ports in the configuration YAML.

EdgeGo: Microsoft Edge Variant

For Edge users, the repository provides EdgeGo with identical 10-channel structure. Usage is interchangeable:

cd %USERPROFILE%\Downloads\EdgeGo
bash clash.meta.sh

The EdgeGo package is maintained in parallel with ChromeGo and receives同步 updates to free server configurations.

Security Considerations

Free Server Risks

The bundled free servers are community-maintained and rotate frequently. For sensitive activities, follow the v2ss self-hosted tutorials to deploy a private V2Ray or Shadowsocks server.

TLS + WebSocket Self-Hosting

The repository includes comprehensive guides for production-grade setups with CDN obfuscation. Example Docker deployment from v2ss/V2Ray之TLS+WebSocket翻墙方法.md:

git clone https://github.com/bannedbook/fanqiang.git
cd fanqiang/v2ss
docker compose up -d

Summary

• ChromeGo is a Windows meta-package with 10 pre-configured proxy channels, not a traditional browser extension
• Download the password-protected 7z archive (jww) and extract to a path without Chinese characters or spaces
• Launch via bash clash.meta.sh for automatic routing or bash start_N.sh for manual protocol selection
• Configure Chrome through system proxy settings, command-line flags, or Proxy SwitchyOmega
• Use ChromeGoMac for macOS and EdgeGo for Microsoft Edge with identical workflows
• Disable Chinese antivirus software before extraction to prevent binary quarantine
• For permanent solutions, follow the v2ss self-hosted server tutorials

Frequently Asked Questions

Is ChromeGo an actual Chrome extension that installs from the Web Store?

No. ChromeGo is a standalone Windows application package that launches proxy clients via bash scripts. It does not install into Chrome's extension system. The name refers to its original bundling with Chrome-based workflows, though it works with any browser or application that supports proxy settings.

Why does ChromeGo use bash scripts on Windows instead of .exe files directly?

The bash scripts in ChromeGo/ handle platform detection, configuration path resolution, and binary selection automatically. This POSIX-based approach maintains consistency with the macOS and Linux packages in the repository. Users need Git Bash (from Git for Windows) to execute them.

How do I know which proxy channel (start_0.sh through start_9.sh) to use?

clash.meta.sh or start_0.sh is the recommended default for general browsing—it provides automatic failover and rule-based routing. Use start_4.sh (Hysteria2) for gaming or real-time applications where low latency matters. Use start_6.sh (NaïveProxy) in heavily censored networks where traffic obfuscation is critical. The specific server quality varies by region and time; experimentation may be necessary.

Can I use ChromeGo's configuration files with other V2Ray or Clash clients?

Yes. The JSON and YAML files in the extracted ChromeGo folder are standard formats. Import config.yaml into Clash for Windows, or v2ray_config.json into V2RayNG on Android. The [android/v2free.md](https://github.com/bannedbook/fanqiang/blob/master/android/v2free.md) tutorial demonstrates this cross-platform compatibility explicitly.

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