CRITICAL BUG: Total Sync Failure - Stale Metadata, Missing History & Total Interface Collapse (Push/Pull Dead)

Google Antigravity
1

Category: Core Extension / Cloud Sync / History Logs Priority: Blocker / Critical

Description: The Antigravity system is suffering from a massive, multi-vector synchronization failure. The metadata bridge is frozen on an old session from 16 days ago, cloud history is not recording recent conversations, and all UI methods for routing conversations between the Manager and the IDE have completely collapsed.

Observed Bug Behaviors:

1. Ghost History & Cloud Desync:

  • Conversations actively happening within the IDE Extension workspace do not appear in the standalone Antigravity Manager app’s history.

  • Entire chat sessions from the last hour are silently ignored and fail to sync to the Cloud completely.

2. Total UI Hook Failure (Push & Pull Mechanisms):

  • PUSH FAILURE: Clicking Open in current window or Open in Workspace from the Manager app fails silently. Even when the correct workspace is open, the command never reaches the IDE.

  • PULL FAILURE: Initially, the Talk in Current Workspace button inside the IDE acted as a workaround, but now even this internal trigger has failed. There is zero communication remaining between the Manager and the IDE process.

3. Dangerous Metadata & Path Desync:

  • Despite the user working in a fresh workspace, the ADDITIONAL_METADATA context persistently reports the “Active Document” from a project session 16 days ago.

  • This creates a severe risk of cross-project code corruption, as the AI model may target the wrong project paths for automated file edits based on this stale metadata.

Expected Behavior:

  • Automatic and live synchronization between the IDE work sessions and the Manager app’s history.

  • Fully functional UI hooks for routing conversation states.

  • Real-time, accurate reporting of the Active Workspace and Focused Document in the AI context.

Technical Notes:

  • Manually purging the local app data folders (specifically code_tracker/active) provided a partial, manual workaround for the metadata desync. However, this is not a viable solution for end-users, and the metadata still fails to update automatically without such invasive measures.

  • The core communication deadlock between the Manager and the IDE (Push/Pull hooks) remains completely unresolved despite the cache purge.

  • The metadata desync appears to be caused by corrupted persistence in the active and history session files.

2

Same, and I noticed that this problem always happen after I restart windows os, but antigravity can read history file in /.gemini/antigravity/brain/ and inject them to current context.

3

Isn’t there a single person in charge here who cares about this massive bug or wants to fix it??