Actually, the most reliable and consistent fix is this simply:
Close your AG IDE,
Install AG 1.16.5 and run it,
Once you open it, it fetches and reloads your history,
Then reinstall your preferred version, a newer one.
This sequence rehydrates the index so history reappears.
The original application saved global states, extension data, and chat windows under a folder named Antigravity. The new standalone IDE looks for these files under a separate directory named Antigravity IDE.
To fix this, you need to move the underlying VS Code database file (state.vscdb) along with your local storage folder
This article will help you recover it: https://thechiddx3.medium.com/how-to-fix-missing-chat-history-in-antigravity-ide-on-macos-1c2f9c3e6582
Bug Report: Windows Path Resolution Bug (Double Slashes) Breaks Conversation History in Antigravity 2.0 Agent
Topic
[Windows] Agent panel shows “No conversations yet” and loses history for all workspaces due to malformed path resolution (//C:/...)
Description
After updating to Antigravity 2.0 on Windows, the Agent panel fails to load any past conversation history associated with workspaces. While the global conversation history is visible, the per-workspace list displays “No conversations yet” under every workspace folder (e.g., C:\WINDOWS\system32, geminifinance, just-dub-it), and the Agent has no access to past context.
This appears to be caused by a path-parsing bug where the IDE passes workspace URIs with a double forward slash prefix (//C:/...) to the language server, which Windows fails to resolve.
Log Analysis
The following errors are thrown repeatedly in the language_server.log when trying to resolve workspace paths:
text
E0601 20:33:10.381292 24232 log.go:398] failed to stat uri: CreateFile //C:/WINDOWS/system32: The filename, directory name, or volume label syntax is incorrect.
E0601 20:33:10.381292 24232 interceptor.go:74] /exa.language_server_pb.LanguageServerService/StatUri (unknown): CreateFile //C:/WINDOWS/system32: The filename, directory name, or volume label syntax is incorrect.
Root Cause
-
The IDE communicates workspace scopes to the Agent’s backend (language_server.exe).
-
The paths are serialized or resolved into //C:/... (e.g., //C:/WINDOWS/system32) instead of standard Windows paths (C:\WINDOWS\system32) or correct file URIs (file:///C:/...).
-
Because Windows treats //C:/... as an invalid network UNC path rather than a local file path, the API CreateFile returns an invalid syntax error.
-
As a result, the database query matching conversation history to the active workspace path fails, rendering the Agent contextually blind to prior workspace conversations.
System Info