Summary
When using both Antigravity CLI (agy) and the Antigravity GUI / IDE on the same machine, conversations initiated from the CLI are completely invisible in the GUI sidebar and /history view. Furthermore, shutting down the GUI’s Language Server overwrites conversation_summaries.db, wiping out unmapped CLI summary records.
Environment
- OS: Windows 11 Pro (x64)
- Antigravity Version: 2.25.0+ (Language Server v2.25)
- Antigravity CLI:
agy
Steps to Reproduce
- Start a conversation using the Antigravity CLI:
agy "Hello, test session" - Verify that the conversation runs and persists in local storage (
~/.gemini/antigravity-cli/conversations/and summaries). - Open the Antigravity GUI / IDE.
- Check the left sidebar (Projects / Conversations) and navigate to
/history.
Expected Behavior
Sessions created via the CLI should appear in the GUI’s conversation history / sidebar under the appropriate project (or “Outside of Project”), allowing the user to seamlessly resume in the GUI without risking database overwrites on shutdown.
Actual Behavior
None of the CLI conversations are visible in the sidebar or in /history. Only conversations originally initiated from within the GUI are displayed, and shutting down the Language Server clobbers non-local records in conversation_summaries.db.
Technical Root Cause & Code Analysis
-
Frontend Filtering in
main.js(CortexTrajectorySource.CLI):- The CLI assigns
CortexTrajectorySource.CLI(source = 17) totrajectory_meta.sourceand inCascadeTrajectorySummary. - In
main.js, the routing function only allows sources0,18, and20:function Wma(source) { return source === CortexTrajectorySource.UNSPECIFIED || // 0 source === CortexTrajectorySource.JETBOX || // 18 source === CortexTrajectorySource.CIDER; // 20 } - When
trajectorySummaries/startStreamreceives updates:updates.filter(([, t]) => Wma(t.source) && !t.trajectoryMetadata?.sourceMetadata?.hideFromConversationList)Wma(17)evaluates tofalse. As a consequence, CLI trajectories are routed intostate.trajectorySummaries.externalSummariesinstead ofstate.trajectorySummaries.summaries. - The UI components for the sidebar (
dl = a => a.trajectorySummaries?.summaries) and/historyexclusively readsummaries(“local”), leavingexternalSummariesas a complete UI dead-end with no user-facing toggle or panel to view them.
- The CLI assigns
-
Destructive Shutdown Flush in Language Server (
reconcile_summaries.go):- Because
language_server.exeonly keeps the “local” subset in its active in-memory summaries cache, upon graceful shutdown it flushes its in-memory map back toconversation_summaries.db. - This flush overwrites the on-disk SQLite database, wiping out or omitting records that were not in its active in-memory set.
- Because
-
Empty Title Omission on Reconciler Startup:
- In
reconcile_summaries.go, trajectories wheretitle == ""are dropped from the startup stream even when a validpreviewstring ortranscript.jsonlprompt exists.
- In
Suggested Fix
- In
main.js, addCortexTrajectorySource.CLI(17) toWma(source), or add a filter toggle in the GUI sidebar (“Show CLI / External Conversations”) so users can browse CLI sessions. - In
language_server.exe, ensure the shutdown flush merges with existing disk state instead of clobbering unmapped records. - Fall back to
previewor the first prompt inreconcile_summaries.goiftitleis empty.