WindGatorRise37/Gemini-Config-Checker-

What it does

Gemini Config Checker tests proxy configurations to see whether they actually reach Google AI Studio and Gemini in a region Google allows. The premise is that HTTP connectivity probes are misleading: Google decides availability per signed-in account after page load, so every live config can look "healthy" while Google still shows a region wall. The tool therefore opens AI Studio and Gemini in a separate browser profile with your Google sign-in and reads what Google displays: AI Studio redirects to its available-regions page, and Gemini shows a not-supported message (why a signed-in browser).

The app has two modes. In Simple mode, each config under test is used directly from your machine. In Advanced mode, a working base config is used as the first hop, and free configs are chained behind it so that you can get a different exit IP. An optional anti-DPI profile applies TLS fragmenting to the route that leaves your machine (anti-DPI profile).

Quick start

The builds are collected on the Releases page. For example, on Windows: unzip the desktop package for amd64 or arm64 and run GeminiConfigChecker.exe. WebView2 is included in Windows 10/11, and the build is unsigned, so SmartScreen may ask you to confirm.

1. In the Scan tab, paste proxy links (vless://, vmess://, trojan://, ss://), a subscription URL, or base64 text, one item per link or line. Alternatively, leave the list empty and select one of the ready-made free lists (user guide).
2. Choose Simple or Advanced. In Advanced mode, you must paste a base config that you know works and that AI Studio does not block.
3. Keep Anti-DPI enabled if plain configs do not connect on your network.
4. Click Sign in with Google once. A browser window opens with a dedicated profile, and sign-in is remembered for later scans. If a browser is unavailable, switch the check type to connectivity-only, which skips region verification.
5. Start the scan and watch the Results tab. Then use the Export tab or the copy buttons to get links or an Xray JSON for your client.

No desktop environment? Run the web server build and open http://localhost:8787 (download options).

Constraints and limits

• Region checking requires Chrome, Edge, or Brave. Without one, only the connectivity test works; Android is connectivity-only because apps cannot drive a signed-in Chromium.
• The README states that only the Windows build has been exercised end to end; macOS, Linux, and Android builds come from CI and have not been run on real devices.
• Region checks take roughly 20–40 seconds per config, and each simultaneous browser check uses about 200 MB of RAM. By default, up to 60 configs are tested.
• Results are a sample: a Cloudflare Worker exit can change between connections, so re-test before relying on a config (results guide).
• Free configs are run by unknown third parties; do not send sensitive traffic through them. The local web server has no authentication, so keep it on localhost (privacy and security).
• Desktop builds are unsigned; Android APKs may be signed with a throwaway key when no repository key is set, so a later build cannot update in place. The README says MIT, while the bundled Xray-core keeps MPL-2.0 (license).

Warnings worth noting

At the top of the README, there is a "Download Gemeni app" button linked to a Dropbox .rar file (download button), which conflicts with the later instruction to fetch builds from GitHub Releases. Treat that outside archive as unrelated to the documented distribution and use the release artifacts and SHA256SUMS.txt instead.

HotRepo's take

The repository appeared on HotRepo's new-project list on 2026-11-15, recording 278 stars in its first observation window with zero forks, and there is no GitHub daily-rank record. That pattern is consistent with a burst of attention around a fresh release rather than evidence of sustained adoption. The project covers a narrow, specific problem — per-account region checks for Google AI Studio and Gemini — with a detailed user guide and a source build path, but the missing real-device testing on macOS/Linux/Android and the conflicting download button are the main things to weigh before relying on it.