I am trying to move the .gemini folder generated by the antigravitycli from my default C: drive to my D: drive to keep my development environment organized.

For context, I already successfully did this for the standard Gemini CLI. For that tool, simply adding the GEMINI_CLI_HOME environment variable pointing to the new D: drive path worked perfectly.

What I have tried for antigravitycli:

• Cut and pasted the .gemini folder to the new location on my D: drive.

• Set new Windows environment variables (GEMINI_CLI_HOME and GEMINI_HOME) pointing to the exact D: drive path.

• Restarted my PC to ensure the variables are loaded.

The Problem:

Unlike the standard Gemini CLI, antigravitycli completely ignores these environment variables. When I launch it, it creates a brand-new .gemini folder back in its hardcoded default location (C:\Users\username\.gemini).

My Constraints:

• I do not want to use directory junctions or symlinks (mklink /J).

• I prefer to avoid writing a custom Batch/PowerShell wrapper script to override the %USERPROFILE% variable.

• I am looking for a native, configuration-based solution.

Is there a specific hidden environment variable, config file flag, or registry tweak that forces the CLI to respect a custom directory path natively?