WestLocksmithSpout/Gemini-Config-Checker-

What it does

Gemini Config Checker tests a list of proxy configs and reports which ones actually open Google AI Studio and Gemini. A plain HTTP probe reports success from any country, so the tool drives a real browser under a Google sign-in and reads what Google shows that account: an AI Studio redirect to /docs/available-regions, or the "Gemini isn't currently supported in your country" wall (why a signed-in browser).

It runs in two modes. Simple checks configs you paste or pull from a subscription against AI Studio and Gemini directly. Advanced takes one working base config and chains free configs behind it, so you can find an exit Google accepts without abandoning your own route. Results can be exported as share links, base64 subscriptions, or full Xray JSON for v2rayN/PattN (user guide).

Quick start

1. Download a build from Releases. Windows users unzip gemini-config-checker-desktop_<version>_windows_amd64.zip and run GeminiConfigChecker.exe; Linux needs libgtk-3-0 and libwebkit2gtk-4.1-0, or you can run the web server build and open http://localhost:8787.
2. Pick Simple or Advanced in the header.
3. Click Sign in with Google. A separate Chrome/Edge/Brave profile opens; the app never sees your password and the profile is deleted by Remove account from app.
4. In Simple mode, paste vless://, vmess://, trojan:// or ss:// links one per line, or enter a subscription URL; leave it empty to scan a bundled free list.
5. Press Start scan and read the Results tab: Healthy, Region blocked, or Error, with per-product AI Studio/Gemini columns and latency.

Android has no signed-in browser path, so the APK only runs connectivity checks and cannot verify region availability.

Constraints

• The project is version 0.1.0 and has only been exercised end to end on Windows; macOS, Linux and Android builds come from CI and have not been run on real devices.
• Region checks need Chrome, Edge, Brave or Chromium. Flatpak browsers cannot be driven; a browser in a nonstandard location is set via GCC_BROWSER or CHROME_BIN.
• Region mode takes roughly 20–40 s per config and about 200 MB of RAM per simultaneous browser check, four by default; the connectivity-only mode is faster but does not check region.
• The web server has no authentication and binds to 127.0.0.1; tunnel it rather than exposing it.
• Desktop builds are unsigned, so SmartScreen and Gatekeeper warn on first launch.
• A verdict is a sample: a Cloudflare Worker exit can change between connections, so results can flip and should be re-tested.
• Free configs are run by unknown third parties; don't send sensitive traffic through them. The repo is Apache-2.0 per its GitHub metadata, while the README states MIT for the project itself and keeps Xray-core under MPL-2.0.

HotRepo's take

The repo appeared on the new-projects list on 2026-11-15, gaining 278 stars in an observation window of about 1.5 hours, with no forks. That is a fast early spike rather than a sustained trend, and there is no GitHub daily-rank record to compare against. For a tool whose whole value is a browser-driven verdict, the notable gap is that only Windows has been run end to end; treat results from the other builds as unverified until the author reports device testing. The project also credits its anti-DPI recipe and scanner logic to other maintainers' work (credits).