I have the same issue, for weeks
It was working, but doesnt work for me now. But then another post say it still works?ā¦
I found that it seems:
if you kept the āAgent Managerā window open when using the Chat in Editor.
the conversation is preserved?ā¦
seems like a index corruption according to this:
Update:
it seem the conversation history + āAgent Managerā methods works, if you are in a āfolderā.
but not, if you are in a āworkspaceā ā¦
be careful with that link and project. the exe may or may not be dangerous.
Have you tried it? Or use the raw python code?
I havent.
Dont blindly trust any open source project.
But normally those antivirus software isnt that accurate eitherā¦
If you can read source, you can see that the .exe has nothing to do with the source at all.
And yes, Iāve tried solving the corruption using similar fixes and even removed the user folder completely, didnāt help, even on new install..
1 Like
I wrote the code. This guy clearly knows nothing about false positives, lol. You can run the Python script instead of the .exe. The .exe is just there so people with less technical knowledge can run it faster. Itās all there on the GitHub page! 4 out of 72 flagged it(false positive) 68 include majors (Kasper, AVAST, ā¦) pass it as safe!!!
1 Like
Thanks, It ās working.
1 Like
Incredible that this is not yet fixed. Are they ditching Antigravity? It is precisely the conversation history that keeps me here from switching to Claude or Codex. Thatās the only sticky part of this service.
None of the other solutions worked properly for me, so I spent just a bit of time creating a solution that had all the functionality I needed.
1 Like
The underlying
.pbconversation data files remain fully intact on disk at~/.gemini/antigravity/conversations/, but the IDEās internal SQLite database (state.vscdb) loses its UI index mappings ā specifically theChatSessionStore.index(JSON) andtrajectorySummaries(Protobuf) ā causing the sidebar to display zero history.This tool rebuilds those internal indices from your intact
.pbfiles, restoring your full conversation history.
That is a good explaination.
NVM. NVM. Not guarantee.
Repeat, following works for me:
Open your workspace.
Open your workspace as a Folder.
Top left > File > Open Folder > Pick your workspace Folder
v
this is important. the conversation only works for a Folder window. Not a Workspace window. (yes, the downside is: you lost the ability to open multiple folders in one workspace)
Click Open Agent Manager on top right, keep it open in the background.
Now the Conversation History will be saved.
Now the Conversation History will be saved.
PS: if your index is corrupted, maybe this wont work anymore? idk?
[Solution] Recovering truncated/missing conversations ā the verbosity: 2 parameter
I lost access to recent conversations in Antigravity and spent hours trying to recover them. The conversations existed as .pb files on disk, but the UI wouldnāt show them and the LanguageServer API (GetCascadeTrajectorySteps) was capping responses at ~819 steps for conversations that had 1,695+ steps. The startIndex and endIndex parameters were completely ignored ā the API always returned the same first 819 steps.
The breakthrough came from reverse-engineering the Antigravity binary. Running strings on the Go binary revealed a component called CascadeClientStepTruncator that uses a verbosity parameter to control how many steps are returned. The default (0) aggressively truncates. Level 1 is moderate. Level 2 disables truncation entirely.
The fix is one parameter:
from antigravity_history.api import call_api
result = call_api(port, csrf, "GetCascadeTrajectorySteps", {
"cascadeId": "<your-cascade-id>",
"verbosity": 2
})
steps = result.get("steps", [])
# Now returns ALL steps, not just the first 819
For my 1,695-step conversation, this returned every single step. The aghistory export tool (pip install antigravity-history) doesnāt use this parameter, which is why its exports are also truncated for long conversations.
Other findings from the binary analysis:
-
The LanguageServer exposes 158+ gRPC methods across 18 services, including
ConvertTrajectoryToMarkdown(which I havenāt tested yet) -
The full service path is
exa.language_server_pb.LanguageServerService -
There are streaming endpoints (
StreamCascadeReactiveUpdates,StreamCascadePanelReactiveUpdates) that might be useful for live monitoring
For the separate indexing bug (conversations exist as .pb files but donāt appear in the sidebar): this is a known issue where the LanguageServer loads conversations into memory on startup but doesnāt persist them to the SQLite store. The aghistory recover tool helps with re-indexing, but has its own bugs (a ValueError: too many values to unpack on line 409 of cli.py ā fix by changing indexed, _ to indexed, _, _ on lines 332, 409, and 470).
Full credit to two Claude instances (Claude.ai and Claude Code CLI) that did the actual detective work ā probing the API, disassembling the binary, and finding the verbosity parameter. I just kept pasting terminal output back and forth.
Hope this saves someone else the hours we spent on it.
4 Likes
If they donāt fix this now with so much information and the literal fixes to so many issues in this threadā¦
1 Like
Itās hard to believe this bug has been around for over a month, through multiple updates, without being fixed.
1 Like
Still facing the same issue.
It is excruciating to be able to see the .pb files in the brain folder, of conversations I literally had last night, and not be able to do anything straightforward to open them. Itās absurd. I really love Antigravity but the continual re-emergence of this missing history bug has worn out my goodwill. It makes no sense that Google, who ostensibly has the most powerful AI model on the planet, with almost unlimited resources, canāt or wonāt pin down such a devastating issue.
You know, if I could just point antigravity to a specific pb file for it to load up, this dependence on some broken automation flow would be nearly moot. Nope. Canāt even inspect the files as text because theyāre binaries. WHY DO CHAT CONVERSATIONS NEED TO BE BINARIES?!
1 Like
Check my comment here for solution:
I just want to give an update. The issue is still not fixed in the latest version of antigravity. I have not updated just restarted my PC and the latest conversation is also just gone.
Youād have to be pretty damn naive to take this risk for no other reason than ātrust me brĆ³ā 
I lost my important history, too. After searching, I found Antigravity_Conversation_Fix.exe was good enough for me.
1 Like