WireProvostPucker/Gemini-Config-Checker-

What it does

Gemini Config Checker tests proxy configurations by opening AI Studio and Gemini in a real signed-in Chromium browser, because Google decides regional availability per account after the page loads. Plain HTTP probes report every live route as healthy, so the tool reads Google's actual verdict instead: an AI Studio redirect to /docs/available-regions or the "Gemini isn't currently supported in your country" message marks a route as blocked. It accepts vless://, vmess://, trojan:// and ss:// links, subscription URLs, or base64 text.

Simple mode tests the configs you already have. Advanced mode chains free configs behind one working base config to obtain a different exit, for cases where Cloudflare routes connect but Google rejects their region. An optional anti-DPI profile reproduces a published fragmentation recipe for filtered networks.

Quick start

1. Download the build for your platform from Releases: Windows amd64/arm64 zip, macOS universal zip, Linux amd64 tarball, or Android arm64 APK. Each release ships SHA256SUMS.txt.
2. Launch GeminiConfigChecker.exe on Windows (the build is unsigned; SmartScreen may ask you to confirm), or extract and run the Linux binary.
3. On first start, use Sign in with Google in the region-check settings; a separate Chrome, Edge or Brave profile opens so the app can read AI Studio and Gemini as a signed-in user. Without a supported browser, switch the check type to connectivity only, which proves reachability but not region.
4. Open the Scan tab, paste one config per line or leave the box empty to use a built-in free list, keep anti-DPI off unless your network needs it, and press Start scan (Ctrl+Enter).
5. Read the Results tab: healthy/connected, region blocked (with per-product status), or error. Use the copy or Export tab to produce a share link, base64 subscription, or Xray JSON.

The same engine is also available as a web server build that serves its UI on http://localhost:8787.

Constraints

• Region checking needs a locally installed Chrome, Edge, Brave, Chromium, Vivaldi or Opera that the app can drive; Flatpak browsers cannot be controlled. Each concurrent browser check uses roughly 200 MB of RAM, and a region check takes about 20–40 s per config.
• Android runs connectivity-only mode, because apps cannot drive a signed-in Chromium there. macOS, Linux and Android builds come from CI and have not been exercised on real devices; only Windows is reported as tested end to end.
• The web server has no authentication. Keep it on localhost or reach it through an SSH tunnel rather than exposing the port.
• A result is a sample: Cloudflare Worker exits can change between connections, so a config may pass now and fail later. Free configs are operated by unknown third parties and are unsuitable for sensitive traffic.
• The README lists MIT, while the repository metadata says Apache-2.0; the bundled Xray-core keeps MPL-2.0 and the fonts keep SIL OFL.

Build from source

Go is required, plus Wails v2 and the platform webview for the desktop app (WebView2, WebKit, or GTK 3 + WebKitGTK 4.1). Android needs the Android SDK, JDK 17+ and Gradle 8.10. The provided Make targets build and test each variant: make test, make web, make desktop, make android, and make dist VERSION=0.1.0.

HotRepo's take

The repository shows one new-list snapshot on 2026-11-15: 268 stars gained in roughly 1.5 hours, with 0 forks and no GitHub daily-rank record. That is a very short window and only one observation, so it supports the fact of a fast early spike but not a trend. The engineering detail visible in the README — a local forwarder implementing per-segment fragment lengths that stock xray-core lacks, selectable client-oriented export formats, and a signed-in verification model — is the part worth evaluating; the distribution channel shown at the top of the README, a Dropbox archive, does not match the Releases instructions and has no stated relationship to the repository's source.