WinnerSpecialist/Gemini-Config-Checker-

What it does

Gemini Config Checker tests proxy configurations not by pinging Google, but by opening AI Studio and Gemini in a browser profile that is signed in to a Google account, then reading the region verdict Google actually shows. According to the README, a plain HTTP probe answers "fine" from every country, so connectivity tests alone cannot tell whether a config gets past the region wall. The supported config formats are vless://, vmess://, trojan://, ss://, subscription URLs, base64 text, and full Xray JSON.

There are two modes. Simple tests a list of configs directly. Advanced chains free configs behind one working base config, useful when a Cloudflare Worker route connects but Google blocks its exit. An optional anti-DPI profile applies TLS ClientHello fragmentation and related settings to the first hop, based on the PattN recipe.

Quick start

1. Download the build for your platform from GitHub Releases; every release includes SHA256SUMS.txt.
2. On Windows, unzip and run GeminiConfigChecker.exe. Windows 10/11 already has WebView2; if SmartScreen warns, choose More info → Run anyway.
3. Open the Scan tab and paste your configs, one per line, or leave the box 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. Keep Anti-DPI on only if plain configs cannot connect in your network.
5. Press Start scan, then check the Results tab for Healthy, Region blocked, or Error. Use Export to copy a link, a base64 subscription, or an Xray config for clients such as PattN or v2rayN.

If no supported browser is installed, or you are on Android, switch the check type to connectivity only in Settings; this drops the sign-in requirement but no longer verifies the region.

Constraints

• Region checking requires Chrome, Edge, Brave, or Chromium. Flatpak browsers cannot be driven. Linux needs a graphical session (DISPLAY or WAYLAND_DISPLAY).
• Region checks run one browser per config at roughly 200 MB RAM each; the default is four simultaneous browser checks and 60 configs per scan.
• Android builds are connectivity-only because apps cannot drive a signed-in Chromium there.
• The web server build serves the UI on http://localhost:8787 with no authentication; keep it on localhost or reach it through an SSH tunnel.
• The binaries are unsigned, and the Android release is signed with a repository key when configured, otherwise with a throw-away key, which prevents in-place updates.
• A verdict is a sample: Cloudflare Worker exits can change between connections, so re-test any config before relying on it.
• The README states version 0.1.0 is an early pre-release exercised end to end only on Windows; macOS, Linux, and Android builds come from CI and have not been tested on real devices.
• The repository has an Apache-2.0 license field, while the README points to MIT for the project and notes Xray-core (MPL-2.0) and fonts keep their own licenses.

HotRepo's take

HotRepo recorded the repository only on the 2026-11-15 new-project list: 286 stars gained in a window of roughly 1.5 hours, 0 forks, with no GitHub daily-rank placement recorded. A star spike with no forks yet and an early pre-release that has been run only on Windows means there is no evidence here of an established user base or of binary-to-source correspondence. The interesting part is the testing method — reading Google's signed-in region verdict instead of relying on HTTP probes — but that method is only worth the trust you place in the released binaries.