Solution to Google Antigravity's no Past History is found. [BUG fix]

Google Antigravity
1

Solution to Antigravity’s no Past History :blush:

Problem: So the problem was, every time we reopen the Antigravity, the past history is gone. Even the new chats are gone. No history saving at all, as it looks like.

Solution: It’s related to the workspace configuration file/path, so the solution is simple. Follow these steps,

1. Open the Google Antigravity editor (Login if you aren’t already).
2. Click on the “Open Agent Manager”. Then you will see “+ Open Workspace” button below workspace.json under Workspaces on the left panel.
3. Click “+ Open Workspace” and click “Open New Workspace” row on the appeared menu.

4. You will be asked to select the project folder, so go ahead.
5. Then on the left panel named Workspaces, you will see the whole Past History in a few seconds loading 1 by 1 (Make sure internet is fine).

6. Now you must click the Close button of the main editor (Not Agent Manager). Then you will be asked to save the configuration to a location on your device, so do it (I saved mine to Documents). Make sure the Agent Manager windows is still open.
7. Now there are 3 dots at the end of the project name under the Workspaces side panel. Click 3 dots and click Focus Editor. Boom you will see the Past History.

Screenshot 2026-03-09 192717
Screenshot 2026-03-09 192717700×629 19.9 KB

8. Congratulations… Now you can see the Past History loaded on the editor.

The idea of the problem I realized.

The problem might be that the editor can’t get the configuration file location or the file is somehow missing, renamed, or the editor is expecting something else, etc,. So creating a new workspace configuration and saving it to a location made it work. But this is temporary.

Since I exposed a solution, people who are smarter will be able to find a permonant solution by somehow,

  1. Saving the workspace file to the exact location editor expects it to be with the correct name.
  2. Any other way.

I got this problem after the version I downloaded on March ‎5, ‎2026. But I hope this works for everyone who are frustrated.

Have a nice day guys!! :blush:

2

Hi @SuneraX
Welcome to the Google AI Forum!!!

Thank you for your valuable feedback. We sincerely appreciate you taking the time to share your thoughts with the community. Your input is crucial for our continuous improvement and we have shared it directly with the relevant internal team.

3

Doesnt work. using windows

4

For me, what worked on Antigravity 1.23.2 on Ubuntu was to first check ~/.gemini/antigravity/conversations to identify the conversation id by the File Modified field and then simply tell the Agent to resume that conversation id. It worked. Model Gemini 3.5 Flash (Medium) to resume with. Not sure if that’s a relevant detail.

5

I use a number of techniques:

  1. I have a “recall-conv” skill that searches the agent’s “brain” for past conversation and resurfaces it in the UI
  2. In my shared disciplines (aka “rules”), I make sure that each artifact the Agent generates has a header with the conversation id - useful for tracking lineage
6

For my purposes, this is of no avail; this anomaly invariably manifests when ‘antigravity’ terminates abruptly, presumably because the system defers its dialogue archiving and uploading sequence to the program’s final shutdown phase. Consequently, precipitously shutting down the operating system triggers the selfsame issue. Under Windows, the conversation logs are indeed preserved in $env:USER/.gemini/antigravity/brain/, where the agent can autonomously locate and retrieve them—especially if the precise date and content of the dialogue are known. However, the agent manager and the historical logs inexplicably roll back by 16 d. Furthermore, utilizing SSH isolates this process; dialogue management over SSH operates independently and remains unaffected, provided the underlying SSH processes are not genuinely terminated.