Installer targets legacy Gemini-CLI settings.json instead of Antigravity 2.0 config directory (resulting in duplicate 273MB binaries)

[uongsuadaubung]

Version

codebase-memory-mcp 0.9.0

Platform

Windows (x64)

Install channel

GitHub release archive / install.sh / install.ps1

Binary variant

standard

What happened, and what did you expect?

When running codebase-memory-mcp install (or using the Windows install.ps1 script), the installer detects and configures the outdated/legacy agent Gemini-CLI rather than Antigravity (the current successor for Antigravity 2.0).

Consequently, it writes the configuration to the deprecated monolithic file C:\Users\<Username>\.gemini\settings.json.
In Antigravity 2.0, the configuration format is modular:

• MCP server configurations must reside in ~/.gemini/config/mcp_config.json
• Hooks configurations must reside in ~/.gemini/config/hooks.json

Because it targets the legacy file ~/.gemini/settings.json, the newly installed MCP server and hooks are completely ignored by the Antigravity 2.0 agent.

Additionally, on Windows, this outdated installation process creates a duplicate binary:

1. C:\Users\<Username>\AppData\Local\Programs\codebase-memory-mcp\codebase-memory-mcp.exe (installed by install.ps1)
2. C:\Users\<Username>\.local\bin\codebase-memory-mcp.exe (copied by the binary's install command)
   Since the binary is ~273 MB, this wastes disk space, and neither copy is recognized by Antigravity 2.0 out-of-the-box because of the incorrect path configuration.

---

Root Cause Analysis

Inside the codebase-memory-mcp binary's install command logic:

1. It looks for and writes to the legacy Gemini CLI agent path: ~/.gemini/settings.json.
2. It has not been updated to detect Antigravity and write sparse configurations to the modern configuration directory ~/.gemini/config/ (specifically mcp_config.json and hooks.json).

---

Expected Behavior

1. The install command should detect the modern Antigravity agent (IDE & CLI).
2. It should write the MCP server configuration to ~/.gemini/config/mcp_config.json instead of ~/.gemini/settings.json.
3. It should write the hooks configuration to ~/.gemini/config/hooks.json using the Antigravity 2.0 hook schema (e.g., using PreToolUse instead of BeforeTool, PreInvocation instead of SessionStart, and outputting JSON {"decision": "allow"} for tool-use checks).
4. On Windows, the installer script install.ps1 and the binary should coordinate on a single binary installation path (e.g., ~/.local/bin/ or AppData/Local/Programs/) to avoid creating two duplicates of the 273 MB binary.

Reproduction

1. Run install.ps1 (or codebase-memory-mcp install -y) on a Windows machine.
2. Observe the command output showing the detection of the outdated agent:

   Detected agents: Gemini-CLI
   
   Gemini CLI:
     mcp: C:/Users/uongsuadaubung/.gemini/settings.json
     instructions: C:/Users/uongsuadaubung/.gemini/GEMINI.md
     hooks: BeforeTool + SessionStart (codebase-memory-mcp reminder)
   

3. Check the generated configuration: it is written to the legacy C:\Users\<Username>\.gemini\settings.json path instead of C:\Users\<Username>\.gemini\config\mcp_config.json.
4. Open the Antigravity 2.0 IDE/CLI and observe that the MCP server is not recognized.

Logs

Diagnostics trajectory (memory / performance / leak issues)

Project scale (if relevant)

No response

Confirmations

• I searched existing issues and this is not a duplicate.
• My reproduction uses shareable code (a dummy snippet or a public OSS repository), not proprietary code.

[DeusData]

Thanks for documenting both symptoms. This report currently combines two separate contracts. The current official Gemini CLI documentation still places user MCP configuration and hooks in ~/.gemini/settings.json, with hook events including BeforeTool and SessionStart: https://github.com/google-gemini/gemini-cli/blob/main/docs/reference/configuration.md. We should therefore not replace the Gemini CLI integration with the proposed Antigravity paths and event names without a canonical Antigravity 2.0 specification and exact product/build identifier. Please link those official references. The duplicate 273 MB Windows binary, however, is a concrete installer-coordination bug and remains tracked in 0.9.1-rc.