Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/cloudwaddie/aitweaker/llms.txt

Use this file to discover all available pages before exploring further.

Gemini feature flags are identified by large integers — there are potentially hundreds of thousands of them. The binary search tool in AI Leaks Tweaker lets you narrow down which specific integer ID activates a feature you have observed, without manually testing flags one at a time. It works by repeatedly halving the candidate range until only one flag remains.

​
How binary search works for flag discovery

When you suspect a feature lives somewhere in a range like 45428766–45999999, it would take an impractical number of individual tests to find it. Binary search solves this by:
  1. Enabling the entire range at once and confirming the feature appears.
  2. Splitting the range in half and enabling only the lower half.
  3. If the feature still appears, discarding the upper half; if not, discarding the lower half.
  4. Repeating until the range collapses to a single flag ID.
Each round halves the search space, so a range of ~500,000 IDs can be narrowed to one flag in roughly 19 steps.

​
Opening the binary search tool

The binary search tool is a separate window launched from the Gemini tab.
1

Go to the Gemini tab

Open AI Leaks Tweaker and click the Gemini tab at the top of the window.
2

Open the Flags sub-tab

Inside the Gemini tab, select the Flags sub-tab.
3

Click Binary Search for Flag

Click the Binary Search for Flag button. A new window titled “Gemini Flag Binary Search” opens and stays on top of the main window.
1

Enter a starting range

In the Min Flag ID and Max Flag ID fields, enter the integer boundaries of your initial search range. The tool defaults to 45428766 and 45999999 — a broad range known to contain active Gemini experiments.
Min Flag ID: 45428766
Max Flag ID: 45999999
Start with a wide range. You can always narrow it in a later session once you have confirmed which thousand-ID band the flag is in.
2

Optionally keep your existing flags enabled

Check Keep current flags enabled if you need your previously saved flags to remain active during the search. This is useful when the feature you are looking for only appears in combination with another flag.
3

Click Start Search

Click Start Search. The tool immediately enables the entire range in rules.json and waits for the Gemini JS bundle to be intercepted by the proxy. The status area shows:
Testing initial range: 45428766-45999999
Waiting for Gemini script load...
The proxy must be running for the tool to detect the script load. Start it from the Proxy tab before opening the binary search window.
4

Reload Gemini in your browser

Switch to your browser and do a hard refresh on gemini.google.com with Ctrl+Shift+R (Windows/Linux) or Cmd+Shift+R (macOS). This forces the page to re-fetch the JS bundle, which the proxy will intercept and modify.Once the proxy logs Modified Gemini script, the Yes and No buttons become active.
5

Answer — is the feature present?

Look for the target feature in Gemini. Then click Yes or No in the binary search window.
  • Yes — the tool narrows to the lower half of the current range and loads it automatically.
  • No — the tool discards the lower half and moves to the upper half.
Repeat the hard-refresh-and-answer cycle for each step.
6

Verify and copy the result

When the range collapses to a single integer, the tool enters verification mode and enables just that one flag. If you confirm the feature is still present, the status shows:
Flag confirmed: 45732101
Click Copy Flag ID to copy it to your clipboard, then add it to your Gemini flags list normally.
If you answer No during the verification step, the tool reports that verification failed and resets. This can happen if the feature requires multiple flags to be active simultaneously. Try re-running the search with Keep current flags enabled checked.
If you already have a promising range but do not need to pin down the exact flag, you can add the range directly from the Flags tab using the Add Range fields.
1

Enter start and end values

Fill in the Start of range and End of range fields in the Flags tab. Both must be positive integers and start must be less than end.
Start of range: 45700000
End of range:   45800000
2

Click Add Range

Click Add Range. The range appears in the flags list in the format 45700000-45800000.
3

Save and test

Click Save Gemini Changes, then hard-refresh Gemini. The proxy logs Modified Gemini ctor when the range has been injected into the script.

​
Managing flags and ranges

Each flag or range in the list has a toggle switch and a notes field.
ControlPurpose
Toggle switchEnable or disable a flag/range without deleting it. Click Save Gemini Changes to persist.
Notes fieldFree-text label (e.g. "deep research variant") to remember what a range does. Saved with the profile.
X buttonPermanently removes the flag or range from the list.
Use the search box at the top of the Flags tab to filter by flag ID or note text. This is helpful when you have accumulated many ranges across multiple search sessions.

​
Frequently asked questions

The buttons activate only when the proxy logs Modified Gemini script. Check that:
  1. The proxy is running (Proxy tab shows Stop Proxy).
  2. Your browser traffic is routed through the proxy (system proxy or FoxyProxy is configured to 127.0.0.1:8000).
  3. The CA certificate is installed — without it, HTTPS interception fails silently in the browser.
  4. You performed a hard refresh (Ctrl+Shift+R), not a normal reload.
The proxy modifies Gemini’s JavaScript by locating the pattern:
ctor(a){return typeof a==="boolean"?a:this.defaultValue}
If Google updates the Gemini JS bundle and this pattern changes, the proxy logs:
[WARN] ctor method not found in <url>
In that case, flags will not be injected even if the proxy is intercepting the request. Check the project repository for an updated proxy.py.
The binary search window does not persist its state between sessions. However, because the search narrows the range with each step, you can note the last tested range from the status label before closing, then re-enter it as the starting range in a new session.
Yes. The flags list supports both formats simultaneously. Ranges are written as start-end (e.g. 45700000-45800000) and exact IDs are plain integers (e.g. 45732101). The proxy handles both in the same injection.
Enable the Keep current flags enabled checkbox before clicking Start Search. When checked, the tool adds the test range on top of your existing enabled flags instead of replacing them. Your original flags are always restored when the search completes or is reset.

Build docs developers (and LLMs) love

Get started for freeTalk to us