The mystery of missing chats in antigravity IDE: from UI glitch to filesystem recovery

Recently, I encountered an unexpected situation in my development environment that many Antigravity IDE users will likely experience.

I had accumulated 64 technical prompt sessions and conversation threads in my history. However, upon opening the IDE sidebar to reference an earlier debugging session, only the 6 most recent conversations were visible. The rest of the history was missing from the standard visual list.

When relying on past AI interactions as an active project knowledge base, losing immediate access to dozens of threads disrupts your workflow. I investigated the underlying behavior to confirm whether session data was corrupted, deleted, or merely constrained by UI rendering logic.

Below is a breakdown of what happens under the hood and the exact steps to access your full conversation history.

Understanding conversation lifecycle and history filters#

Antigravity IDE manages chat states through a hybrid system of local cache and contextual scopes. When the interface hides older sessions, it typically traces back to three factors:

1. Workspace scoping filter (project folder): The sidebar defaults to filtering conversations associated with the currently open workspace root.
2. Implicit UI pagination: The sidebar renders the most recent sessions without an explicit "load more" button.
3. Post-update path migration: Version updates adjusting local directory hierarchies (globalStorage).

Step-by-step recovery guide#

1. The active workspace filter#

The sidebar prioritizes displaying sessions started within the project directory currently open in the editor:

• What happens: If you open a different project folder, switch repositories, or start a scratch window without an open folder, threads from other contexts are hidden from the primary sidebar list.
• Solution: Reopen the exact project root directory where the original sessions were created.

2. The global agent command: /resume#

To access any of your 64 conversations regardless of current workspace filters, use the native CLI conversation selector:

1. Click into the chat prompt input box.
2. Enter the command:

/resume

1. Press Enter.

This brings up the Conversation Picker overlay. Within this selector:

• Use the up and down arrows (↑ / ↓) to highlight conversations on the current page.
• Use the left and right arrows (← / →) to page through older historical records.

3. Inspecting local storage on Linux#

If specific sessions remain inaccessible following client updates, verify where the IDE persists SQLite databases and JSON state files.

On Linux, Antigravity manages local data across two primary locations:

A. AI engine brain storage directory#

Inspect the internal agent brain session directory in your terminal:

# Inspect active AI engine and brain state files
ls -la ~/.gemini/antigravity-ide/brain/

# Check for backup snapshots following updates:
ls -la ~/.gemini/antigravity-backup/ 2>/dev/null

B. IDE global storage directory#

Because the editor architecture is built on the VS Code ecosystem, serialized plugin and UI states reside in globalStorage:

ls -la ~/.config/Antigravity/User/globalStorage/

C. Version-independent state discovery#

To locate metadata databases and state dumps regardless of folder structure changes:

# Discover state databases (.vscdb/.sqlite) and configuration files (.json)
find ~/.config/Antigravity -iname "*.vscdb*" -o -iname "*.sqlite*" -o -iname "*.json" 2>/dev/null | head -20

These directories contain SQLite databases and session dumps proving historical records remain fully intact on disk.

4. Forcing a UI reindex#

If session files exist on disk but the sidebar remains stuck on 6 entries due to renderer cache delays:

1. Open the IDE Command Palette: Ctrl + Shift + P
2. Run the command:

Developer: Reload Window

This restarts interface renderer processes and re-reads metadata pointers from disk.

Conclusion: UI scoping vs disk persistence#

In this guide, I walked through the exact steps I used to recover all 64 conversation threads: verifying the active workspace directory, triggering the global conversation selector with /resume, and inspecting globalStorage and the brain directories on disk when necessary.

Maintaining prompt history is essential when I use the IDE as an extension of my daily reasoning. In the vast majority of cases, your history is never lost — it is simply outside the current UI scope or waiting to be surfaced via the /resume picker.

See also

Infrastructure How to restart the XFCE4 desktop without logging out or rebooting

Infrastructure Linux troubleshooting: when 'command not found' made me revisit PATH and sudo su

Development Migrating tools to Python 3.13 on Kali Linux: from TLS handshakes to c-api changes

This post is licensed under CC BY-NC.