WingDataVacuum/Gemini-Config-Checker-

What it does

Gemini Config Checker tests proxy configs (vless, vmess, trojan, ss) against Google AI Studio and Gemini and reports which routes actually work. A plain HTTP probe is not enough: Google decides regional availability per signed-in account after the page loads, so HTTP checks can mark every live config as healthy. The app therefore drives a separate Chromium profile you sign into, opens AI Studio and Gemini, and reads the block signals: AI Studio redirecting to /docs/available-regions, or Gemini showing an unsupported-country message (why a signed-in browser).

Two modes share one switch:

• Simple tests configs you provide, or a ready-made free list, as a direct route from your machine.
• Advanced places free configs behind a working base config, so the free configs exit through that base and you get a different egress that Google may accept.

It also applies an anti-DPI profile (TLS ClientHello fragmentation and related settings) for networks where plain configs do not connect, and can export the results as share links, base64 subscriptions or a ready-to-import Xray config.

Getting started

1. Get a build from the Releases page and pick the package for your platform. Releases ship SHA256SUMS.txt.
2. Windows: unzip and run GeminiConfigChecker.exe; WebView2 is built into Windows 10/11 and the build is unsigned, so SmartScreen may warn. macOS: move the .app to Applications and right-click → Open on first launch. Linux: install libgtk-3-0 and libwebkit2gtk-4.1-0, unpack the tarball and run ./GeminiConfigChecker.
3. Open the Scan tab, paste one config per line (vless://, vmess://, trojan://, ss://), a subscription URL or base64 text, or leave it empty to test a ready-made free list.
4. Click Sign in with Google. A separate Chrome / Edge / Brave profile opens; sign in there and the window closes when sign-in is detected. The app never sees your password.
5. Press Start scan (or Ctrl+Enter) and watch the Results tab fill in.

On Android there is an APK (arm64-v8a), but it runs connectivity-only mode because Android cannot drive a signed-in Chromium; region availability is not checked there. The web server build serves the same UI on http://localhost:8787 (download and install).

Constraints and caveats

• Region checking needs Chrome, Edge, Brave or Chromium; Flatpak browsers cannot be driven. No browser means switching to connectivity-only, which proves reachability but not regional access.
• Region checks take roughly 20–40 s per config and each simultaneous browser check uses about 200 MB of RAM; defaults are 4 browser checks and 20 connectivity tests, with up to 60 configs per scan.
• A verdict is a sample, not a guarantee. A Cloudflare Worker exit can change between connections, so a route may pass now and fail later; re-test before relying on it.
• The build is unsigned and the web UI has no authentication, so keep it on localhost or tunnel it instead of exposing it. Free configs are operated by unknown third parties; traffic destinations are visible to them.
• The desktop builds have been run end to end on Windows only; macOS, Linux and Android builds come from CI and have not been exercised on real devices. The README also states the license is MIT while the repository metadata lists Apache-2.0, so verify the license before redistribution.
• The README shows a Dropbox-hosted .rar download button at the top alongside the Releases instructions; prefer the Releases assets with checksums, since the archive's contents and origin are not described.

Building from source

Building requires Go, plus Wails v2 and the platform webview for the desktop app; Android needs the Android SDK, JDK 17+ and Gradle 8.10. The Makefile targets are make web, make desktop, make android, make dist VERSION=<version> and make test (build from source).

HotRepo's take

A new repository with a narrow, concrete problem: validating proxy routes against Google's actual signed-in regional behavior rather than a generic ping. The strongest technical point is that it reads Google's own block signals instead of trusting connectivity probes. The caveats are equally concrete: desktop testing so far is Windows-only, the region check depends on a desktop Chromium, and verdicts can flip between connections. The mismatched download buttons and license metadata are worth checking before use or redistribution.

HotRepo 点评

这个项目解决的是一个具体而窄的问题：用真实的登录态浏览器判断代理线路能否进入 Google AI Studio 和 Gemini，而不是靠通用连通性探测。技术上的关键点在于读取 Google 自己的拦截信号，而不是相信 ping 结果。局限也很明确：桌面端目前只在 Windows 上完整跑通，区域检测依赖桌面 Chromium，且结论可能随连接变化。使用或再分发前，下载入口和许可证元数据的不一致值得核对。