VortexHostFeel/Gemini-Config-Checker-

What it does

Gemini Config Checker helps you find which proxy configurations actually reach Google AI Studio and Gemini. Instead of sending a plain HTTP probe, it opens the two products in a separate browser profile where you are signed in, then reads what Google shows: a redirect to the available-regions docs for AI Studio, or the unsupported-country message for Gemini. The project author argues this is necessary because a bare request answers "fine" from every country Why a signed-in browser.

There are two modes:

• Simple tests each of your configs (vless/vmess/trojan/ss links, a subscription URL, base64, or a built-in free list) as the route from your machine to Google.
• Advanced puts a working base config first and chains free configs behind it, useful when Cloudflare reachability is fine but Google rejects that exit.

Results include healthy/blocked/error status per product, latency, filtering and bulk copy. Exports come as share links, a base64 subscription, or an Xray JSON config, with a variant that includes or strips the fork-specific finalmask field.

The engine is built on Xray-core, the desktop shell on Wails, and native builds target Windows, macOS, Linux and Android.

Getting started

Prebuilt binaries are on the Releases page; each release also ships SHA256SUMS.txt for verification. The Windows desktop build is the only one the author says has been run end to end; the others come from CI.

1. Download the archive for your platform and unzip it. On Windows, run GeminiConfigChecker.exe. The build is unsigned, so SmartScreen may show a warning; the README instructs choosing More info → Run anyway.
2. On Linux, install the runtime first: sudo apt install libgtk-3-0 libwebkit2gtk-4.1-0, then run ./GeminiConfigChecker. Without a desktop environment, use the web server build (./gemini-config-checker) and open http://localhost:8787 web server.
3. In the Scan tab, choose Simple or Advanced.
4. Paste configs one per line, or leave the box empty to test a ready-made free list.
5. Keep Anti-DPI on if plain Cloudflare configs do not connect on your network.
6. Click Sign in with Google once; a separate browser profile opens, sign in normally, and the window closes when the session is detected.
7. Press Start scan (or Ctrl+Enter) and read the Results tab.
8. Use Copy / Copy with chain or the Export tab to move working configs into v2rayN, Hiddify, PattN or a BPB chain field.

For Advanced mode, the base config is tested first; if it cannot reach Google the scan stops with a message.

Constraints

• The region check needs Chrome, Edge, Brave or Chromium locally, and each concurrent browser check uses roughly 200 MB of RAM (default 4 simultaneous).
• Android runs in connectivity-only mode: it can prove a route reaches Google but cannot verify the region, because apps cannot drive a signed-in Chromium.
• A verdict is a sample. Cloudflare Worker exits can change between connections, so a passing config may fail later and should be retested.
• The web server listens on 127.0.0.1 but has no authentication; keep it local or tunnel it rather than exposing it.
• The anti-DPI profile is intended for filtered networks; elsewhere it only adds latency. Only fragment masks are supported, and per-segment lengths are handled by a local forwarder rather than stock Xray-core.
• Free configs are run by unknown operators; the README warns not to send sensitive traffic through them.
• The license is MIT, while the bundled Xray-core and fonts keep their own licenses.

HotRepo's take

This is a young project: HotRepo recorded its first snapshot on 2026-11-15 with 192 stars and the whole gain of 192 stars within a single one-hour new-board window, with no forks. That reflects a fast initial burst rather than a sustained trend, and no GitHub daily rank has been recorded. The tool targets a real measurement problem — Google's region verdict is only visible to a signed-in user — and its README is unusually honest about unsigned builds, untested CI platforms, and results being samples. The main thing to watch is provenance: the README also pushes a third-party Dropbox .rar at the top, which does not match the Releases-based distribution described later.