[BUG] Antigravity Agent Manager: Conversation history exists on remote host but is not listed or creatable after latest update (Remote SSH, Mac & Ubuntu)

Google Antigravity
35

FWIW those guides are not about agent manager or ssh (the focus of this thread).

36

I can reproduce a closely related issue on a local Windows workspace, without Remote SSH.

Environment:

- Windows 11

- Antigravity 1.23.2 (Antigravity.exe ProductVersion/FileVersion 1.23.2)

- Local workspace opened as `C:\code\doc`

- The conversation picker shows the current workspace as `doc`

- This started after switching Google accounts in Antigravity

Observed behavior:

- New conversations created from the top-right ā€œNew conversationā€ button are stored on disk and have brain logs under `%USERPROFILE%\.gemini\antigravity\ā€¦`.

- The brain logā€™s active document is inside `C:\code\doc`.

- The same conversations appear under ā€œOther Conversationsā€ instead of ā€œRecent in docā€.

- Restarting Antigravity does not fix it.

- A recent affected conversation title was ā€œReviewing Recent Git Logsā€.

Local state evidence:

- The workspace state uses the encoded URI `file:///c%3A/code/doc` in `google.antigravity` / `antigravity.workspaceCascadeMap`.

- New records in `antigravityUnifiedStateSync.trajectorySummaries` are written with workspace field values like `file:///c:/code/doc` (unescaped colon), sometimes with repo metadata.

- Older records that appear correctly under ā€œRecent in docā€ use field 9 like:

  • `1 = file:///c%3A/code/doc`

  • `2 = file:///`

- If I manually normalize the summary recordā€™s workspace field to the encoded form, the same conversation immediately moves from ā€œOther Conversationsā€ to ā€œRecent in docā€.

- The next newly created conversation is written in the plain URI form again and falls back to ā€œOther Conversationsā€.

This looks like a URI normalization / exact-match bug in the conversation index rather than data loss. It would be helpful if Antigravity canonicalized workspace URIs before grouping conversations and migrated existing `trajectorySummaries` records.