Hi team,
I’m running into an issue where one of my conversations no longer loads in the app, even though I’ve confirmed the underlying data is still present on disk. Details below.
Environment:
- OS: Windows
- Antigravity install path: AppData\Local\Programs\antigravity
- Trajectory ID: db54fc49-9e65-425a-b723-7a314b9e76..
Issue:
When I open the affected conversation or start a new message in it, I get the following error in the UI:
[unknown] trajectory not found: db54fc49-9e65-425a-b723-7a314b9e76..
The conversation no longer appears correctly in the sidebar/history.
Troubleshooting already completed:
1. Ran `git config --unset extensions.worktreeconfig` in the project directory — no change.
2. Checked main.log at %APPDATA%\Antigravity\logs — found an unrelated auto-updater error (sha512 checksum mismatch during a background update download), which I believe is a separate issue but flagging in case it’s connected.
3. Verified the trajectory folder still exists and contains data:
.gemini\antigravity\brain\db54fc49-9e65-425a-b723-7a314b9e76..
This folder contains populated .system_generated\messages and .system_generated\steps subfolders with hundreds of intact, non-empty JSON files, plus task/artifact files with recent timestamps. So the raw conversation data itself appears intact.
4. Based on this, it looks like the issue is with the sidebar index (likely state.vscdb under %APPDATA%\Antigravity\User\globalStorage\) being out of sync with the actual data in the brain folder, rather than the data being deleted.
What I’d like help with:
- Guidance on safely rebuilding or repairing the conversation index so this trajectory (and any others affected) shows up again in the sidebar
- Confirmation on whether it’s safe to reinstall Antigravity without losing the state.vscdb index, or whether that file needs to be handled separately during a reinstall
- Any official tooling or steps to resync the index against the brain folder
I’ve backed up state.vscdb before making any further changes, and I’m holding off on reinstalling until I hear back, since I understand that can sometimes wipe the very index needed for recovery.