[Radar] Track Gemini CLI to Antigravity CLI transition

[luoyuctl]

Background

Google has announced that Gemini CLI users should migrate to Antigravity CLI. agenttrace currently lists Gemini CLI as a supported local coding-agent session source, so this transition is relevant to parser coverage, onboarding clarity, and future compatibility positioning.

This is only a radar item. There is not yet enough local trace evidence to create a parser or docs implementation task.

Evidence

• Google Developers Blog announced Transitioning Gemini CLI to Antigravity CLI and states that Gemini CLI users can continue the workflow in Antigravity CLI: https://developers.googleblog.com/an-important-update-transitioning-gemini-cli-to-antigravity-cli/
• Google I/O 2026 developer highlights say Google encourages Gemini CLI users to migrate to Antigravity CLI: https://blog.google/innovation-and-ai/technology/developers-tools/google-io-2026-developer-highlights/
• Duplicate check on 2026-05-20 for Antigravity Gemini CLI transition parser and Gemini Antigravity found no existing matching issue in this repository.

User value

Users who currently expect Gemini CLI session coverage need a clear future answer about whether Antigravity CLI produces compatible local history, changed paths, changed event formats, or different tool/cost/session evidence.

Adoption rationale

Tracking the transition early helps keep parser coverage and onboarding language aligned with the active coding-agent ecosystem without promising support before a real local artifact is verified.

Suggested scope

• Keep this as radar until Antigravity CLI local session artifacts are available for inspection.
• Compare Antigravity CLI local history paths, event schema, tool-call records, token/cost fields, and session identity fields against existing Gemini CLI parsing.
• If promoted later, split into a narrow parser or docs task with a fixture-backed acceptance check.
• Keep existing Gemini CLI wording unless public evidence shows it has become misleading for active users.

Non-goals

• Do not add Antigravity CLI parser support without a local fixture or reproducible sample.
• Do not remove Gemini CLI support from public docs based only on migration messaging.
• Do not claim Antigravity CLI compatibility before validating local artifacts.
• Do not create package, release, or external posting work from this radar item.

Acceptance criteria

• Maintainer or future Product review decides whether this remains radar, becomes a parser task, or becomes a docs compatibility task.
• Any promoted task names the exact local artifact path or event schema being validated.
• Any parser work includes a minimal fixture or reproducible local sample.
• Public copy remains conservative and distinguishes existing verified Gemini CLI support from unverified Antigravity CLI compatibility.

Suggested lane

lane/radar, priority/P2, status/needs-human

Risk

Medium. The ecosystem signal is strong, but implementation risk is high without artifact-level evidence. Acting too early could introduce incorrect parser claims or confuse existing Gemini CLI users.

Source

source/radar: ecosystem scan on 2026-05-20. Tavily MCP was not exposed in this session, so Product used search fallback and prioritized official Google sources.

[luoyuctl]

Event: Evidence
Actor: Product
Scope: #236
State change: none; keep lane/radar,status/needs-human
Evidence: Ecosystem scan on 2026-05-20 could not use Tavily because no Tavily MCP tool was exposed in this session, so Product used search fallback. New community-level evidence suggests Antigravity may have local history artifacts, but still not enough for parser implementation:

• antigravity-history community tool claims Antigravity stores conversations in encrypted protobuf files and exports via a local language-server API while the app is running: https://www.reddit.com/r/google_antigravity/comments/1rrg5xt/export_and_recover_antigravity_conversations_open/
• A user migration thread reports needing to copy ~/.gemini, ~/.antigravity, and ~/.config/Antigravity to move conversation history between devices, with path/username sensitivity: https://www.reddit.com/r/google_antigravity/comments/1s35zp5/moving_conversations_history_from_a_device_to/
• Public Antigravity docs currently describe local folder/repository association, but do not document a stable session trace/export schema for downstream parsers: https://antigravity.google/docs
  Product read: this strengthens [Radar] Track Gemini CLI to Antigravity CLI transition #236 and narrows the future investigation surface, but it remains unofficial and artifact-insufficient. If promoted later, require a reproducible local sample or fixture and verify whether the source is encrypted protobuf, a local language-server API, copied .gemini history, or another stable export. Do not claim Antigravity compatibility from these signals alone.
  Next owner: Human / Product monitor

[luoyuctl]

Event: Evidence
Actor: Product
Scope: #236
State change: none; keep lane/radar,status/needs-human
Evidence: Ecosystem scan on 2026-05-20 could not use Tavily because no Tavily MCP tool was exposed in this session, so Product used search fallback and prioritized official docs. Antigravity CLI docs now expose an official local configuration path, but still do not document a stable session-history or trace schema for downstream parsers:

• Antigravity CLI authentication docs list ~/.gemini/antigravity-cli/settings.json for CLI settings and describe OAuth/API-key configuration: https://antigravity.google/docs/cli/authentication
• Antigravity CLI command reference documents Gemini-compatible commands and output modes, but does not provide a supported local session artifact contract for conversation history, tool calls, token usage, or failure events: https://antigravity.google/docs/cli/commands
  Product read: this is stronger official path evidence than prior community-only history signals, but it is still not enough for parser implementation. If promoted later, require a reproducible local sample or fixture and verify whether usable evidence lives in CLI settings, an export command, copied Gemini history, encrypted app storage, or another stable artifact. Do not claim Antigravity compatibility from configuration-path evidence alone.
  Next owner: Human / Product monitor

[luoyuctl]

Event: Evidence
Actor: Product
Scope: #236
State change: none; keep lane/radar,status/needs-human
Evidence: Ecosystem scan on 2026-05-20 could not use Tavily because no Tavily MCP tool was exposed in this session, so Product used search fallback and prioritized official sources. Google Developers Blog now has an official migration timeline for Gemini CLI to Antigravity CLI: https://developers.googleblog.com/an-important-update-transitioning-gemini-cli-to-antigravity-cli/

Product interpretation:

• This strengthens the radar signal from adjacent/possible migration to an official ecosystem transition.
• The adoption risk is real for users who rely on Gemini CLI local history and may later expect continuity in agenttrace reports.
• It still does not provide a stable Antigravity CLI session-history schema, local trace artifact, public fixture, or reproducible sample that would justify parser implementation.

Routing: keep as radar. Future promotion should require a real Antigravity CLI local artifact or documented trace/session schema and should be scoped narrowly to source detection, parser confidence notes, or docs wording. Do not claim Antigravity CLI support from this evidence alone.

[luoyuctl]

Event: Evidence
Actor: Product
Scope: #236
State change: none; keep lane/radar,status/needs-human
Evidence: Ecosystem scan on 2026-05-20 could not use Tavily because no Tavily MCP tool was exposed in this session, so Product used search fallback and prioritized official Antigravity docs. New official docs add stronger product-surface evidence but still no stable parser artifact:

• Antigravity CLI features docs describe ~/.gemini/antigravity-cli/settings.json, plugin staging under ~/.gemini/antigravity-cli/plugins/<plugin_name>/, /resume, /rewind, /tasks, /agents, subagent panels, and full subagent detail views with tool execution logs: https://antigravity.google/docs/cli-features
• Using AGY CLI docs describe /resume, auto-save resume behavior, and ~/.gemini/antigravity-cli/keybindings.json: https://antigravity.google/docs/cli-using
• Agent Settings docs state app-local data lives under ~/.gemini/antigravity/ and includes Artifacts and Knowledge Items: https://antigravity.google/docs/agent-settings

Product interpretation:

• This strengthens the adoption rationale for tracking Antigravity as a future local-session surface: conversations, resume/switch, subagent logs, tasks, and app-local artifacts are all official user-facing concepts.
• It still does not document a stable session-history schema, JSONL/protobuf contract, export command, token/cost event fields, tool-result failure fields, or public fixture that would justify parser implementation.

Routing: keep as radar. Future promotion should require a concrete local artifact or documented trace/session schema, then split narrowly into source detection, parser confidence notes, or docs wording. Do not claim Antigravity support from docs-only evidence.
Next owner: Human / Product monitor

[reaworks-ops]

This radar item becomes actionable as soon as there is one messy local Antigravity session artifact, not before. Otherwise the parser task risks being shaped by blog/docs language instead of the real trace boundary.

ReaWorks can do a $25 quick Antigravity trace evidence map: send one redacted local session/config/history sample, and I’ll return the candidate file paths, stable vs unstable fields, what must be excluded as secrets, and 3 parser acceptance checks for agenttrace.

The proof/acceptance for that review would be simple: a short markdown note plus a minimal fixture outline showing which fields are observed, inferred, or still unchecked. If you get one real Antigravity run artifact, that’s enough input for the pass.

[luoyuctl]

Event: Decision
Actor: Product
Scope: #236
State change: none; keep lane/radar,status/needs-human
Evidence: Latest Product review after the non-owner artifact-mapping offer and a fresh official-source scan found no maintainer-provided Antigravity local session artifact, public fixture, or reproducible trace sample.
Decision: keep this radar parked. A paid or external review offer is not an implementation signal by itself. Future promotion requires one concrete redacted local artifact, documented stable trace/session schema, or reproducible sample that shows paths, event fields, token/cost evidence, tool-result/failure evidence, and secret-exclusion boundaries.
Next owner: Human / Product monitor
Guardrail: Do not create parser/docs implementation work, claim Antigravity support, request private logs publicly, or route external paid review work without maintainer authorization.

[luoyuctl]

Event: Evidence
Actor: Product
Scope: #236
State change: none; keep lane/radar,status/needs-human
Evidence: Ecosystem scan on 2026-05-20 could not use Tavily because no Tavily MCP tool was exposed in this session, so Product used search fallback and prioritized trace-surface evidence. A third-party PyPI package, antigravity-history, now provides a more inspectable version of the earlier community signal: it claims Antigravity conversations are stored as .pb files and that export/recovery works by connecting to Antigravity local LanguageServer API while Antigravity is open with a workspace: https://pypi.org/project/antigravity-history/
Product read: this narrows the likely future investigation surface to local .pb conversation files and/or a local LanguageServer API, but it is still not a stable official session-history contract and it does not provide an agenttrace-ready fixture. Keep this radar parked until a maintainer-provided redacted artifact, documented schema, or reproducible sample proves which fields are stable enough for parser confidence notes or docs wording.
Next owner: Human / Product monitor
Guardrail: Do not create parser implementation, claim Antigravity support, or depend on third-party recovery tooling without fixture-backed acceptance checks.