weldbladesmithwharf/Gemini-Config-Checker-

What It Does

Gemini Config Checker takes a list of proxy configs (vless://, vmess://, trojan://, ss://, subscription URLs, base64 lists, or a ready-made free list) and tests each one by opening Google AI Studio and Gemini in a separate Chrome/Edge/Brave profile that you have signed into. It does not trust a bare HTTP probe, because Google decides region availability per signed-in account after the page loads; a blocked result shows as a redirect to the available-regions page for AI Studio or the "not supported in your country" message for Gemini.

Two modes cover different questions. Simple tests each config directly from your machine. Advanced takes one working base config and chains free configs behind it, so you can get a different exit when the base connects but Google rejects its region.

Quick Start

1. Download the build for your platform from the Releases page and unzip or install it. Windows ships GeminiConfigChecker.exe; macOS a universal .app; Linux a tarball that needs libgtk-3-0 and libwebkit2gtk-4.1-0; Android an arm64 APK. Every release includes SHA256SUMS.txt.
2. Launch the app. On Windows, SmartScreen may warn because the build is unsigned; choose More info → Run anyway.
3. In the Scan tab, paste your configs one per line, or leave the box empty to use a ready-made free list.
4. Click Sign in with Google. A browser opens in an isolated profile; sign in normally and the window closes when detected.
5. Press Start scan (or Ctrl+Enter) and watch the Results tab; then use the copy/export buttons to get the links or an Xray config for your client.

The web server build serves the same UI at http://localhost:8787: run ./gemini-config-checker, optionally with -addr and -no-open.

Constraints

• The README states Version 0.1.0 has only been run end to end on Windows; macOS, Linux and Android builds come from CI and have not been exercised on real devices.
• Region checking needs Chrome, Edge, Brave or Chromium and a graphical session; Flatpak browsers cannot be driven. Android cannot drive a signed-in Chromium and therefore only supports connectivity-only checks, which do not verify the region.
• Browser checks are slow (20–40 s per config) and memory-heavy (about 200 MB per simultaneous check).
• Anti-DPI defaults are aimed at filtered networks, especially Iran; they add latency elsewhere. Stock Xray cores cannot parse the fork's finalmask schema, so the export offers a standard variant that strips it.
• The web UI has no authentication; keep it on localhost or tunnel it.
• A pass is a sample, not a guarantee: Cloudflare Worker exits can change between connections.
• Free configs are operated by unknown third parties; the README warns against sending sensitive traffic through them.
• Releases are unsigned. The README's download section also links a Dropbox-hosted .rar archive, which is not a source build and should be treated separately from the release artifacts.

HotRepo's take

The project appeared on the new-project list on 2026-11-15 with 288 stars gained in the reported window and no forks. The repository's own description promises Windows/macOS/Linux/Android, but the README is explicit that only Windows has been exercised end to end, so the platform matrix is broader on paper than in testing. Given that the main deliverables are unsigned precompiled binaries and an APK, and that the release signing identity is not tied to the repository key, readers should confirm the artifacts they run against SHA256SUMS.txt and the source layout described in the README before trusting results from a build.

Project source and documentation