TurtleReside/Gemini-Config-Checker-

What it does

Gemini Config Checker tests proxy configs (vless, vmess, trojan, ss share links, subscription URLs or base64 lists) and reports which ones actually let a signed-in user open Google AI Studio and Gemini. The premise is that plain HTTP probes return "fine" from every country, so the tool drives a real Chrome/Edge/Brave profile signed in with a Google account and reads Google's own verdict: AI Studio redirecting to /docs/available-regions, or the Gemini "not currently supported in your country" notice (why a signed-in browser).

It has two modes. Simple checks your configs directly. Advanced chains free configs behind a working base config, so you can swap the exit that Google sees. Both use an optional anti-DPI profile (TLS ClientHello fragmentation, fingerprint, ALPN and cipher-suite settings from the PattN recipe) implemented by a local forwarder (anti-DPI profile). Results can be copied as links, base64 subscriptions, or a full Xray JSON config, with finalmask fields included for PattN/PattNG or stripped for stock Xray/v2rayN.

Getting started

Download a build from the Releases page and check it against the published SHA256SUMS.txt (download and install). On Windows, unzip the windows_amd64 (or arm64) archive, run GeminiConfigChecker.exe, and use More info → Run anyway if SmartScreen warns, since the build is unsigned. Linux needs libgtk-3-0 and libwebkit2gtk-4.1-0; the web-server build runs with ./gemini-config-checker and serves the UI at http://localhost:8787. Android ships an arm64-v8a APK.

In the app:

1. Choose Simple or Advanced in the header.
2. Paste share links, a subscription URL or base64 one per line, or leave the box empty to test a bundled free list.
3. Keep Anti-DPI on only if you are behind network filtering.
4. Click Sign in with Google: a separate browser profile opens, you sign in normally, and the window closes when sign-in is detected.
5. Press Start scan and read the Results tab; a region-mode check takes roughly 20–40 seconds per config.

Constraints

• Region checking needs Chrome, Edge, Brave, Chromium or Vivaldi on the machine, or the GCC_BROWSER / CHROME_BIN variable pointing at one; Flatpak browsers cannot be driven.
• Android and connectivity-only mode prove reachability and latency but do not verify region, because Android apps cannot drive a signed-in Chromium.
• Each simultaneous browser check uses about 200 MB of RAM; the default cap is 60 configs and 4 browser workers.
• A verdict is a sample: Cloudflare Worker exits can change between connections, so re-test before relying on a config.
• The web server has no authentication and binds to 127.0.0.1; do not expose it without a tunnel.
• macOS, Linux and Android builds come from CI and, per the README, had not been exercised on real devices as of v0.1.0.
• Free configs are operated by unknown third parties; the README itself warns against sending sensitive traffic through them.
• The README states an MIT license, while the repository metadata lists Apache-2.0; the bundled Xray-core keeps MPL-2.0 (license).

HotRepo's take

The project entered the new-project board on 2026-11-15 with 192 stars in its first recorded hour, which is a fast start for a v0.1.0 pre-release. The documentation is unusually detailed for that stage — platform-specific install paths, CI/release rules, and an explicit caveat that only Windows has been exercised on hardware. Two details deserve attention before installing: the README's top banner links to a Dropbox .rar rather than the Releases artifacts described in the text, and the repository's license metadata disagrees with the README. Neither is disqualifying — Releases are the documented path and SHA256 checksums are published — but readers should use the Releases page and verify the checksum rather than the badge link.