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.

Profiles are named sets of configuration that each store a proxy command and per-app settings for Gemini, Copilot, Google Labs, and Grok. You can maintain as many profiles as you like — for example, one for everyday use and another for testing experimental flags — and switch between them instantly from the top of the main window.

​
What a profile stores

Every profile contains a proxy_command string and an apps object with one entry per supported app. Here is the complete structure of the default profile from profiles.json:
profiles.json
{
    "proxy_command": "mitmdump -s proxy.py -p 8000 --ssl-insecure",
    "apps": {
        "gemini": {
            "enabled": true,
            "flag_configs": {
                "45730924": { "note": "Default Tools", "enabled": true },
                "45691404": { "note": "Search", "enabled": true },
                "45707395": { "note": "Agent Mode", "enabled": true }
            }
        },
        "copilot": {
            "enabled": true,
            "flags": [
                { "name": "share-to-invite", "enabled": true },
                { "name": "tv-lumi", "enabled": true }
            ],
            "allow_beta": true
        },
        "google_labs": {
            "enabled": true,
            "music_fx_replace": "debug",
            "bypass_not_found": true
        },
        "grok": {
            "enabled": true,
            "config_json": "{}",
            "spoof_subscription": false
        }
    }
}
The file also has a top-level active_profile field that persists across sessions so the app reopens on the last-used profile, and an app_settings object for tray and startup preferences that are shared across all profiles.

​
Switching profiles

The Profile dropdown at the top of the window lists all saved profiles. Selecting a different profile immediately reloads the entire UI with that profile’s data and regenerates rules.json, which the proxy picks up automatically.
Switching profiles restarts the proxy if it is running, so the new flag set takes effect without any manual action.

​
Creating, renaming, and deleting profiles

1

Create a new profile

Click New. A dialog asks for a name. The new profile is pre-populated with the same default structure (proxy command, empty flag lists, all apps enabled) and immediately becomes the active profile.If you enter a name that already exists, the creation is cancelled and an error is logged.
2

Rename the active profile

Click Rename. A dialog pre-fills the current name. Enter the new name and confirm. The profile data is preserved; only the key in profiles.json changes.If you enter a name that already exists, the rename is cancelled and an error is logged.
3

Delete the active profile

Click Delete. The active profile is removed and the first remaining profile becomes active.
You cannot delete the last remaining profile. If only one profile exists, the delete operation is blocked and an error is logged.

​
Importing and exporting profiles

Profiles can be shared as standalone .json files. The exported file contains only the profile data itself — not the active_profile or app_settings fields.
1

Export the active profile

Click Export. A save dialog opens pre-filled with <profile-name>.json. Choose a location and save. The file contains the full proxy_command and apps object for the active profile.
2

Import a profile from a file

Click Import. Select a .json file. The app uses the filename (without extension) as the profile name.If that name is already taken, a dialog prompts you to enter a different name before the import proceeds.
You can import profiles shared by other users directly. Any valid profile JSON file is accepted as long as it follows the apps structure.

​
Legacy profile migration

Older versions of AI Leaks Tweaker stored flag_configs and modification_enabled at the root level of each profile rather than nested under apps. When the app loads profiles.json, it automatically detects and migrates any profile in the old format to the current apps-based structure, then saves the updated file. No manual action is required. The migration runs silently at startup and is logged in the proxy log panel.
before migration (old format)
{
    "flag_configs": { "45730924": { "note": "", "enabled": true } },
    "modification_enabled": true
}
after migration (new format)
{
    "apps": {
        "gemini": {
            "enabled": true,
            "flag_configs": { "45730924": { "note": "", "enabled": true } }
        }
    }
}

Build docs developers (and LLMs) love

Get started for freeTalk to us