New Adapter: Google Antigravity

Traces CLI v0.6.4 retires direct support for Gemini CLI, following Google's own move away from it. Your past Gemini CLI sessions stay visible in Traces. In its place, Traces now supports Google Antigravity CLI and IDE sessions.

What "retired" means for Gemini CLI

Under the hood, gemini-cli moved from the active agent list into LEGACY_AGENT_IDS. On retirement, an id is removed from SUPPORTED_AGENT_IDS and the CLI adapter registrery, which blocks new share, setup, and discovery for that agent.

But nothing you already shared disappears. Historical Gemini CLI traces keep their correct name ("Gemini CLI"), logo, and accent color through the frontend's AgentId-keyed maps, so old traces render exactly as before

Meet the Antigravity adapter

Antigravity happens to store its data under ~/.gemini, but it's a distinct agent (antigravity, not Gemini CLI). Traces reads sessions from all three Antigravity storage roots and surfaces them under one Antigravity agent:.

• ~/.gemini/antigravity-cli/brain/... The CLI
• ~/.gemini/antigravity/brain/… Antigravity 2.0
• ** ~/.gemini/antigravity-ide/brain/…** The legacy IDE

The CLI writes a richer transcript_full.jsonl; the IDE writes only transcript.jsonl. Traces prefers the full transcript and falls back to the plain one, so both the CLI and IDE work without any per-source setup

How Traces reads an Antigravity session

Each transcript is JSONL with one record per line, ordered by step_index, Traces normlizes those records into a common trace shape:

• Full turns. User prompts (USER_INPUT), assistant reasoning and text (PLANNER_RESPONSE with thinking/content), tool calls, and tool results each map to their own trace event, preserving the complete conversation.
• Tool calls and results. Antigravity records carry no call id, so Traces pairs each result to the most recent preceding call by step order (FIFO as the tie-breaker). Built-in tools like run_command, view_file, grep_search, and list_dir are recognized by result type.
• Compaction. A CHECKPOINT record surfaces as a compaction system event with its sequence number and summary.
• Subagent. When Antigravity spawns children, it records them in an INVOKE_SUBAGENT record in the parent transcript. Traces reads those conversationId links and connects each child to its parent.

Future record types Antigravity might add aren't dropped. Traces falls back to whatever readable text they carry, so nothing goes silently missing.

What you can do now

• Share Antigravity sessions. Run `traces share --agent antigravity1 to publish a session.
• CLI and IDE are both supported. Sessions from any of the three roots surface. under the single Antigravity agent.