bingshuo/guanghu
1
0
Fork 0
Code Issues Pull Requests Actions 4 Packages Projects Releases Wiki Activity
guanghu/docs/adr/0147-antigravity-cli-agent-adapter.md
Guanghu Domestic Migration 9b41d51231
Some checks are pending
Auto-update PR branches / Update open PR branches (push) Waiting to run
Details
CI / Frontend Static Quality Checks (push) Waiting to run
Details
CI / Frontend Tests & Coverage (push) Waiting to run
Details
CI / Rust Tests & Quality Checks (push) Waiting to run
Details
CI / Linux build verification (push) Waiting to run
Details
Deploy docs / Build VitePress site (push) Waiting to run
Details
Deploy docs / Deploy to GitHub Pages (push) Blocked by required conditions
Details
Release (Alpha) / Compute alpha version (push) Waiting to run
Details
Release (Alpha) / Build release artifacts (push) Blocked by required conditions
Details
Release (Alpha) / GitHub Release (alpha) (push) Blocked by required conditions
Details
Release (Alpha) / Update docs and release pages (push) Blocked by required conditions
Details
chore: import sanitized domestic snapshot for REPO-004 
Source snapshot: 514ab1975951d94342ea38e64101d5a0f1c51c77
2026-07-17 15:55:28 +08:00

2.6 KiB
Raw Permalink Blame History

type, id, title, status, date, supersedes
type id title status date supersedes
ADR 0147 Antigravity CLI agent adapter active 2026-06-28
0091
0097

Context

ADR-0091 and ADR-0097 made Gemini CLI the Google-backed CLI agent path for durable external MCP setup and app-managed AI panel sessions. Antigravity CLI is now the maintained successor path, with official one-shot execution through agy -p ... --cwd, dedicated Antigravity MCP configuration in ~/.gemini/config/mcp_config.json or workspace .agents/mcp_config.json, and continued support for GEMINI.md / AGENTS.md workspace rules during Gemini CLI migration.

Keeping gemini as Tolaria's product-facing local-agent id would leave users pointed at deprecated setup docs and the old ~/.gemini/settings.json MCP shape.

Decision

Tolaria replaces the app-managed Gemini CLI agent with an Antigravity CLI adapter.

The product-facing local agent id is antigravity. Existing stored gemini default-agent values and legacy status payloads normalize to antigravity so older settings do not get dropped.

The desktop backend:

  • discovers agy through PATH, login-shell lookup, and common local install locations, including ~/.local/bin/agy
  • runs agy -p <prompt> --cwd <vault> from the active vault
  • writes transient workspace MCP config to .agents/mcp_config.json for app-managed sessions
  • maps Safe mode to --sandbox=true --toolPermission=proceed-in-sandbox
  • maps Power User mode to --sandbox=false --toolPermission=always-proceed
  • avoids --dangerously-skip-permissions
  • streams line-oriented stdout into Tolaria AI panel text events and reports setup/auth failures with Antigravity-specific recovery copy

Durable external MCP setup now writes the standard Tolaria MCP entry to ~/.gemini/config/mcp_config.json for Antigravity CLI instead of the legacy Gemini CLI ~/.gemini/settings.json path. The optional vault-root GEMINI.md compatibility shim remains valid because Antigravity CLI continues to parse Gemini-compatible context files during migration.

Consequences

  • Users see Antigravity CLI in agent pickers, onboarding, command registry, and install links.
  • Older default_ai_agent: "gemini" settings continue to select the Google-backed CLI path after migration.
  • Existing standalone Gemini CLI global config is no longer mutated by Tolaria's durable MCP setup.
  • Antigravity end-to-end native QA requires agy to be installed and authenticated; local tests use fake executables for deterministic command/config coverage.
  • Future Antigravity CLI flag changes must update the adapter tests and this ADR rather than silently falling back to dangerous bypass flags.