AG2 project identity mapping corruption / same folderUri split into multiple project UUIDs

Google Antigravity
1

Hi Antigravity team and community,

I am seeing a serious project identity / local state corruption issue in Antigravity 2.x.

The same local workspace folder is being split into multiple projects in Agent Manager. Over time, the sidebar shows multiple duplicated entries for what is actually the same folder, for example:

  • 2

  • 3

  • …

From looking at the local files, it appears that the same folderUri is being assigned multiple different project UUIDs under:

~/.gemini/config/projects/

This seems to fragment the project identity rather than simply rendering a duplicate UI item. My concern is that conversations, summaries, and workspace mappings may be split across different project IDs.

This does NOT look like only the previously mentioned “duplicate projects when importing from Antigravity 1.0” issue. I am seeing this in AG2 during normal usage / new sessions.

Environment:

  • OS: macOS Tahoe 26
  • Antigravity version: 2.0.1
  • Install/update path: auto upgraded from AG1
  • number of duplicate project entries same as the conversations
  • Did it start after an update? yes

What I observed:

  1. Open the same workspace folder in Antigravity.
  2. Use Agent Manager / start new agent sessions.
  3. After some sessions or restarts, the same workspace appears as multiple separate projects.
  4. Inspecting ~/.gemini/config/projects/ shows multiple project JSON files that appear to point to the same folderUri but have different IDs.
  5. Existing conversations appear to be split across these duplicate project entries.

Expected behavior:

  • One stable project identity per folderUri.
  • Starting a new session should reuse the existing project UUID for that folderUri.
  • Updates/migrations should not create additional project IDs for the same local folder.
  • If duplicate project IDs already exist, Antigravity should provide an official repair/migration tool.

Actual behavior:

  • The same folderUri gets split into multiple projects.
  • Agent Manager becomes fragmented.
  • Conversation history / summaries may be associated with different project UUIDs.

Safety concern:
There are community scripts/workarounds that attempt to fix this by editing files under:

~/.gemini/config/projects/
~/.gemini/antigravity/agyhub_summaries_proto.pb
~/.gemini/antigravity/conversations/*.db

However, some of these approaches appear risky because they may do raw UUID byte replacement inside protobuf/DB files, choose a canonical project automatically, and do not always provide rollback or validation.

Could the Antigravity team clarify the official safe recovery path?

Questions:

  1. Is this a known AG2 bug separate from the Antigravity 1.0 import duplicate-project issue?
  2. Which local files are authoritative for project identity and conversation-to-project mapping?
  3. Is it safe for users to edit ~/.gemini/config/projects/ manually, or can that orphan conversations?
  4. Should agyhub_summaries_proto.pb or conversation DB files ever be modified by users?
  5. Is there an official repair tool or migration script planned?
  6. Is there a supported way to force Antigravity to re-index conversations and consolidate project IDs safely?
  7. What files should users back up before attempting any repair?

I have not run destructive repair scripts yet. I can provide anonymized examples of the duplicated project JSON entries, folderUri values, and counts if useful.

Thanks.

2

I solved it by

  1. Clear Cache Index
    Delete or move the local cache file:
    ~/.gemini/antigravity/agyhub_summaries_proto.pb

    Terminal command (rename as backup)

    mv ~/.gemini/antigravity/agyhub_summaries_proto.pb ~/.gemini/antigravity/agyhub_summaries_proto.pb.bak

  2. Reset Migration Flag
    Edit the state config file:
    ~/.gemini/antigravity/antigravity_state.pbtxt
    Find the migrate_convos_into_projects line and change its value to MIGRATION_STATUS_UNSPECIFIED

    Terminal command

    sed -i ‘’ ‘s/MIGRATION_STATUS_COMPLETED/MIGRATION_STATUS_UNSPECIFIED/’ ~/.gemini/antigravity/antigravity_state.pbtxt

  3. Restart the Gemini client. The system will re-run the migration process.

Optional tip: Back up the entire ~/.gemini directory before making changes, just in case.