The morning after one update, my sidebar was empty. Hours of design discussion from the night before, gone — or so I thought. It took a few stomach-turning minutes to realize that what had vanished wasn't the conversations. It was the table of contents.
Here's the short version up front: an empty history panel very often means the index is broken while the conversation files are still on disk. Below is how I check that, how I rebuild the index, and the habits I use now so a bad morning costs me minutes instead of hours.
Two different kinds of "gone"
An empty panel can mean the conversation files are truly lost, or only that the sidebar index is empty. The official forum has several reports of history disappearing after a restart while the files remain on disk, and in my experience the second case is by far the more common.
Here is how I read the symptoms before touching anything:
| What you see | Likely cause | First thing to try |
|---|---|---|
History panel empty, but brain/ has fresh files | Only the sidebar index is empty | Rebuild the index (below) |
| Empty in one folder only | A different workspace is open | Open the folder you used last |
Empty only when opened via a .code-workspace file | Open-method quirk | Open the folder directly |
brain/ holds only old files | The data is actually gone | Check backups or Time Machine |
Three quick checks before digging in:
- Open a different folder. History is tied to what you have open, so you may simply be in another workspace
- Open the project folder itself, not a
.code-workspacefile. Forum reports link the workspace-file route to a missing history - Update and restart. History bugs do get fixed in releases, so check the official download page first
If none of that helps, look at the disk.
Check whether the conversations still exist
Conversation data lives under .gemini in your home directory. Forum reports show today's files accumulating in two folders:
- macOS / Linux:
~/.gemini/antigravity/brain/and~/.gemini/antigravity/conversations/ - Windows:
C:\Users\<you>\.gemini\antigravity\brain\and the neighboringconversations\
ls -lat ~/.gemini/antigravity/brain/ | head -20
ls -lat ~/.gemini/antigravity/conversations/ | head -20On Windows, PowerShell does the same check:
Get-ChildItem "$env:USERPROFILE\.gemini\antigravity\brain" | Sort-Object LastWriteTime -Descending | Select-Object -First 20
Get-ChildItem "$env:USERPROFILE\.gemini\antigravity\conversations" | Sort-Object LastWriteTime -Descending | Select-Object -First 20If you see files dated around the day you lost the history, the conversations aren't gone — the UI just can't see them. brain/ holds the working notes and plans the agent produced per conversation, and they're readable text, so you can usually reconstruct what was decided. If everything is old, jump to the last section.
Rebuild the sidebar index
The sidebar list is drawn from an index stored in state.vscdb, a SQLite file, like other VS Code-based editors. In the forum thread I followed, the telltale sign was an empty antigravityUnifiedStateSync.trajectorySummaries key in ItemTable.
macOS : ~/Library/Application Support/Antigravity/User/globalStorage/state.vscdb
Windows: %APPDATA%\Antigravity\User\globalStorage\state.vscdb
Linux : ~/.config/Antigravity/User/globalStorage/state.vscdbSome builds use an Antigravity IDE folder name instead; if you can't find the file, look one level up from globalStorage. Quit Antigravity completely before touching anything.
If you see sidecar files such as state.vscdb-wal or state.vscdb-shm next to state.vscdb, copy those along with it. Copying after a full quit also avoids catching a half-written state.
# 1. Back up first
cp "$HOME/Library/Application Support/Antigravity/User/globalStorage/state.vscdb" \
"$HOME/state.vscdb.bak-$(date +%Y%m%d)"
# 2. Inspect the index key
sqlite3 "$HOME/Library/Application Support/Antigravity/User/globalStorage/state.vscdb" \
"SELECT key, length(value) FROM ItemTable WHERE key LIKE '%trajectorySummaries%';"
# 3. Delete the row so the IDE rescans local conversations on next launch
sqlite3 "$HOME/Library/Application Support/Antigravity/User/globalStorage/state.vscdb" \
"DELETE FROM ItemTable WHERE key = 'antigravityUnifiedStateSync.trajectorySummaries';"If sqlite3 isn't installed (it usually isn't on Windows), Python's standard library can do the same inspection and delete. Save this as check_index.py:
import sqlite3, sys
con = sqlite3.connect(sys.argv[1])
key = "antigravityUnifiedStateSync.trajectorySummaries"
row = con.execute("SELECT length(value) FROM ItemTable WHERE key = ?", (key,)).fetchone()
print("value length:", row[0] if row else "no row")
if len(sys.argv) > 2 and sys.argv[2] == "--delete":
con.execute("DELETE FROM ItemTable WHERE key = ?", (key,))
con.commit()
print("deleted")Run python check_index.py <path to state.vscdb> to look only; the delete happens only if you add --delete. I tried inspect, delete, inspect again against a throwaway database to make sure it behaves. "no row" means the index entry is already gone.
Relaunch and see whether the list returns. I'll be honest: in what I've read, confirmed full recoveries with this are rare, and some users report cloud sync overwriting local edits at every launch. I treat it as a worthwhile attempt when the files are intact, not a guaranteed fix.
Even if the sidebar stays empty, typing @ in a new chat and opening the Conversations tab can pull an older conversation back in — the cheapest way to reuse the context.
Four habits that cost me almost nothing
Early on I trusted the history panel like a vault. That did not end well. My rule now: the panel is a convenience; the files are the record.
- Copy decisions into your own files right away. Design conclusions and hard-to-reproduce debugging notes go into something like
docs/decisions/ - Open projects the same way every time. Folder-first removes one variable when something looks wrong
- Snapshot
.gemininightly. I run this fromlaunchdon macOS:
#!/bin/bash
SRC="$HOME/.gemini/antigravity"
DST="$HOME/Backups/antigravity"
mkdir -p "$DST"
find "$DST" -name "antigravity_*.tar.gz" -mtime +30 -delete
tar -czf "$DST/antigravity_$(date +%Y%m%d).tar.gz" -C "$(dirname "$SRC")" "antigravity"To run it nightly on macOS, drop a plist like this into ~/Library/LaunchAgents/ and launchctl load it (swap in your username):
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key><string>local.antigravity.snapshot</string>
<key>ProgramArguments</key>
<array><string>/bin/bash</string><string>/Users/your-username/bin/antigravity_snapshot.sh</string></array>
<key>StartCalendarInterval</key>
<dict><key>Hour</key><integer>23</integer><key>Minute</key><integer>30</integer></dict>
</dict>
</plist>Remember chmod +x on the script, and run it by hand once on the day you set it up. I don't trust a backup until I've seen the file appear.
- Copy
state.vscdbbefore big updates. It takes seconds and leaves you one way back
If it still isn't there
- Time Machine / File History: if enabled, an older copy of
.geminimay be recoverable - Sign out and back in from the account icon at the bottom left to redo the sync. One user reported losing work doing this, so back up the folder first
Related reading: fixing settings sync that won't work and workspace indexing stuck.
One thing to do today
You can rebuild an index, but you can't rebuild what was in the files. Before anything else, copy ~/.gemini/antigravity somewhere safe — that single step is what I'd ask of you today.