[Bug] Conversations in Remote-SSH workspace are never added to history (trajectorySummaries not updated) - v2.5.5

Google Antigravity
1

Environment

  • Antigravity IDE 2.5.5 (server build ecfbad74d93962fc8ca485d93ab9b4f3d4c*****)
  • Client: Windows
  • Remote: Linux NAS via Remote-SSH (language server started with --app_data_dir antigravity-ide)
  • Migrated from Antigravity 1.x to Antigravity IDE around 2026-08-20
  • “Check for Updates” reports no updates available

What happens
The conversation history list only shows about 8 conversations from roughly one month ago. Every conversation created since then is missing from the list, so I cannot go back to any recent conversation after restarting.

What I verified

  1. Conversation data IS saved on the remote host: ~/.gemini/antigravity-ide/conversations/ contains 57 .db files, including today’s, and brain// folders are created normally.
  2. The history index on the Windows client is %APPDATA%\Antigravity IDE\User\globalStorage\state.vscdb, key antigravityUnifiedStateSync.trajectorySummaries. It contains only 9 conversation IDs. 49 conversations that exist on the remote host are not in it.
  3. As a test, I backed up state.vscdb and deleted only the trajectorySummaries key. After restarting, the history list was empty and was not rebuilt from the remote conversations.
  4. I then created a new conversation, fully exited (File > Exit) and restarted. The new conversation did not appear in the history list either.

Expected
Conversations created in a Remote-SSH workspace should be registered in the history index and remain visible after restart.

Questions

  • Is this a known issue with Remote-SSH in 2.5.x?
  • Is there a supported way to rebuild the history index from the remote conversations folder?
2

Hi @ogiya,

Your conversations on the NAS are safe. Only the history list on Windows is missing them.

The list isn’t rebuilt by scanning the folder. It only updates when the remote server sends each conversation over, and with Remote-SSH those updates aren’t getting through. That’s also why deleting the key left it empty, so please don’t do that again.

What you can do:

  1. Exit the IDE fully and restore your state.vscdb backup to get your old list back.
  2. Create a conversation in a local Windows folder and restart, so we can tell whether only Remote-SSH is affected.
  3. In View > Output, look for “Failed to push update for topic trajectorySummaries” and send us any matching lines.
  4. To carry on with a missing conversation, ask the agent: “Read ~/.gemini/antigravity-ide/brain// and summarize where we left off.”

Let me know is the issue resolves or the issue still persists?