wisemeadowlarkspike/Gemini-Config-Checker-
Security & PrivacyScans proxy configs by testing them in a signed-in browser to see which reach Google AI Studio and Gemini.
What it does
Gemini Config Checker tests proxy configurations by reproducing what Google actually checks. Its premise is that plain HTTP probes are useless here: Google decides region availability per signed-in account after the page loads, so a request from almost any country can answer "fine". Instead, the tool drives a real Chrome, Edge or Brave window over each candidate route and looks for the documented block signals: a redirect to /docs/available-regions on AI Studio, and the "not supported in your country" message on Gemini (why a signed-in browser).
It accepts vless://, vmess://, trojan:// and ss:// share links, subscription URLs, base64 blobs, or a ready-made free list. Two modes cover different questions: Simple tests your own configs directly; Advanced puts a working base config in front of free configs so they exit through its tunnel. The proxy engine is Xray-core; a built-in anti-DPI forwarder reproduces the fragmenting recipe used by PattN (anti-DPI profile).
Getting started
Prebuilt desktop apps, web-server binaries and an Android APK are published on the Releases page. Take the build matching your OS and architecture; each release ships SHA256SUMS.txt.
Windows:
- Unzip
gemini-config-checker-desktop_<version>_windows_amd64.zip. - Run
GeminiConfigChecker.exe. WebView2 ships with Windows 10/11; the binary is unsigned, so SmartScreen may ask you to choose More info → Run anyway.
Linux (desktop build):
sudo apt install libgtk-3-0 libwebkit2gtk-4.1-0
tar -xzf gemini-config-checker-desktop_<version>_linux_amd64.tar.gz
./GeminiConfigChecker
Without a desktop environment, use the web-server build: ./gemini-config-checker, then open http://localhost:8787.
First run in the UI:
- Pick Simple or Advanced in the header.
- Paste configs one per line, or leave the box empty to use a bundled free list.
- Click Sign in with Google. A browser window in a separate profile opens; the app never sees your password. Sign-in completes when the window closes by itself.
- Press Start scan (
Ctrl+Enter) and watch the Results tab. In region mode a config is "healthy" when the products you selected load without the region wall.
If no supported browser is installed, switch the check type to connectivity only in settings: no sign-in, no browser, but the region is not verified, only reachability and latency.
Constraints
- Region checking requires Chrome, Edge, Brave, Chromium or Vivaldi. Flatpak browsers cannot be driven; set
GCC_BROWSERorCHROME_BINfor non-standard locations. - macOS, Linux and Android builds come from CI and have not been exercised on real devices; only Windows is confirmed to work end to end. Android is connectivity-only because apps cannot drive a signed-in Chromium.
- Browser checks cost roughly 200 MB of RAM each (default 4 concurrent); region checks take 20–40 s per config, with a default cap of 60 configs per scan.
- A verdict is a sample: a Cloudflare Worker exit can change between connections, so re-test any config before relying on it.
- The web-server UI has no authentication; keep it on localhost or reach it through an SSH tunnel.
- Sign-in cookies live only in an isolated profile. Free configs are operated by unknown third parties and should not carry sensitive traffic.
- The README states MIT, while the bundled Xray-core keeps MPL-2.0 and the fonts their SIL OFL terms.
HotRepo's take
The repository surfaced on the new-project board on 2026-11-15, recording 264 stars in a window of roughly 1.5 hours and no forks — a very short, very concentrated burst with no daily all-language rank recorded. The engineering story in the README is unusually specific for a project of this age: it names the exact block signals Google shows, credits the anti-DPI recipe and fragmenting fork it reproduces, and states plainly which platforms are untested. The weak point is distribution: a prominent button at the top of the README points to a .rar on Dropbox, while the installation section directs users to GitHub Releases, and the desktop builds are unsigned. For a tool that handles Google account sign-in and runs third-party proxy configs, that split is where readers should look closest.
Written by AI from the project's README, updated . The project's own docs are the source of truth.
You might also like
- ultimateriderpulley/Gemini-Config-Checker-Scans proxy configs by signed-in browser checks to see which ones can actually reach Google AI Studio and Gemini.
- Violetnyudress/Gemini-Config-Checker-Tests proxy config chains to see which ones reach Google AI Studio and Gemini in a signed-in browser.
- TurtleReside/Gemini-Config-Checker-Scans proxy configs to find ones that reach Google AI Studio and Gemini from a signed-in browser.
- WingDataVacuum/Gemini-Config-Checker-Test proxy configs in a signed-in browser to see which ones actually reach Google AI Studio and Gemini.
- TypeTyrantScheme/Gemini-Config-Checker-Test proxy configs in a signed-in browser to see which ones actually reach Google AI Studio and Gemini.