Product: Antigravity (VSCode fork by Google) Affected Versions: 1.19.6 (app 1.107.0), 1.20.5 Platform: Windows 11 Pro (10.0.26200) Date: 2026-03-12
Summary
The “Past Conversations” button in the Gemini chat panel is permanently disabled (greyed out, cursor-not-allowed, opacity-50). Conversations are saved to disk as .pb files under ~/.gemini/antigravity/conversations/, but the trajectorySummariesProvider Zustand store never gets populated, leaving the button disabled.
Additionally, the / slash command list shows “No matching results” in version 1.20.5 (not reproducible in 1.19.6).
Version-Specific Behavior
| Feature | 1.19.6 | 1.20.5 |
|---|---|---|
| Chat (conversation execution) | Works | Works |
| Past Conversations button | Disabled | Disabled |
/ slash commands |
Works | “No matching results” |
Conversation .pb files written |
Yes | Yes |
Due to the / command regression in 1.20.5, testing was primarily done on 1.19.6.
Root Cause Analysis
Data Flow (Expected)
LS (language_server_windows_x64.exe)
→ GetAllCascadeTrajectories RPC
→ extension host (extension.js)
→ workbench (workbench.desktop.main.js)
→ trajectorySummariesProvider._setStateFromSync(data)
→ UI reads Object.keys(store.summaries).length > 0
→ button enabled/disabled
What Actually Happens
-
LS starts normally: Discovery file confirms LS version 1.19.4 (bundled with app 1.19.6).
-
trajectorySummariesProvideris initialized empty:// workbench.desktop.main.js this.trajectorySummariesProvider = this.D(new pB({summaries: {}}, () => {})) -
Sync mechanism exists but never fires:
this.D(Ri(s => { const r = e.read(s), o = i(r); n._setStateFromSync(o) // ← never called })); this.trajectorySummariesProvider = n;The reactive signal
enever produces data, so_setStateFromSyncis never invoked. -
Button stays disabled:
// hasPastConversations check (1.19.x: kWc, 1.20.x: Muu) h = Object.keys(d.summaries).length > 0 // always false -
Conversation files exist on disk at
~/.gemini/antigravity/conversations/*.pbbut are never read back into the UI’s trajectory summaries store.
Key Evidence
-
[AG-PATCH]confirmed that calling_setStateFromSync({summaries: {...}})on the FINAL provider reference (after the second assignment) correctly enables the button and populates the picker. -
The first
trajectorySummariesProviderassignment is overwritten by a second one — only the second reference is live. -
The
.pbfiles are protobuf-encoded and cannot be read without the schema. -
The
getDiagnosticscommand (per open-source SDK analysis) should returnrecentTrajectories[].summarywith human-readable titles, but this data never reaches the workbench store.
Additional Error (1.20.5 only)
Console shows repeated errors on startup:
[createInstance] wre depends on UNKNOWN service agentSessions.
This agentSessions service is missing, which may explain the / command and other agent-related feature failures in 1.20.5.
Steps to Reproduce
-
Clean install Antigravity 1.19.6 or 1.20.5 on Windows 11
-
Sign in with Google account
-
Open Gemini chat panel, start a conversation
-
Close the conversation
-
Observe: “Past Conversations” button (clock icon) is greyed out
-
Check
~/.gemini/antigravity/conversations/—.pbfiles exist
Expected Behavior
The “Past Conversations” button should be enabled after at least one conversation exists, showing a picker with conversation summaries.
Workaround
A PowerShell patch script is available on Gist and as an attachment (ag-patch-conversations.ps1) that:
-
PATCH 1: Forces
hasPastConversations = trueby appending||!0to the length check -
PATCH 2: Forces the selector function (
kWcin 1.19.x,Muuin 1.20.x) to returntrue -
PATCH 3: Injects an IIFE after the final
trajectorySummariesProviderassignment that populates the store with conversation IDs read from the.pbfilenames on disk
The script supports both 1.19.x and 1.20.x pattern variants.
Limitations:
-
Conversation titles are not available (shows truncated UUID + file size instead) because protobuf decoding would require the schema
-
Must be re-run after creating new conversations (renderer process cannot access filesystem)
-
Patch is lost on app update/reinstall
Usage
# Apply patch
powershell -ExecutionPolicy Bypass -File ag-patch-conversations.ps1
# Restore original
powershell -ExecutionPolicy Bypass -File ag-patch-conversations.ps1 -Restore
Suggested Fix Areas
-
Primary: Investigate why the reactive signal feeding
_setStateFromSyncon thetrajectorySummariesProvidernever fires. The LS’sGetAllCascadeTrajectoriesRPC (protobuf message 135/136) should return conversation data. -
Secondary: The
getDiagnosticscommand’srecentTrajectoriesarray (confirmed by SDK analysis) contains summaries with titles — this data should feed the store. -
1.20.5 specific: The missing
agentSessionsservice ([createInstance] wre depends on UNKNOWN service agentSessions) likely causes the/command and other agent features to fail.