Summary
When using the “Undo” function on a message that is not the first message in a conversation within Antigravity’s Agent Manager (Playground), the entire conversation disappears from the UI, even though the underlying data files remain intact on disk.
Environment
| Component | Details |
|---|---|
| Application | Google Antigravity |
| OS | Pop!_OS 22.04 LTS (Ubuntu-based) |
| Date Occurred | December 10, 2025 |
| Affected Conversation ID | 6385c54b-84ee-4421-b647-a2334fa14922 |
| Conversation Title | “Antigravity Update on Pop!_OS” |
Steps to Reproduce
- Open Antigravity and navigate to the Agent Manager (Playground section)
- Open an existing conversation with multiple messages
- Navigate to a message that is NOT the first message in the conversation
- Click the “Undo” button/option on that message
- Result: The entire conversation disappears from the Agent Manager sidebar
Expected Behavior
The undo function should:
- Revert only the selected message to its previous state, OR
- Remove only that specific message while keeping the conversation visible
Actual Behavior
The undo function:
Removes the entire conversation from the Agent Manager UI- The conversation no longer appears in the Playground sidebar
- The conversation cannot be accessed through the UI
Technical Investigation
Files That Still Exist After the Bug
The following files were confirmed to exist on disk after the conversation disappeared:
1. Conversation Data File (Protocol Buffer)
/home/enerby/.gemini/antigravity/conversations/6385c54b-84ee-4421-b647-a2334fa14922.pb
Size: 920,123 bytes
Last Modified: December 9, 2025, 17:05
2. Brain/Artifacts Directory
/home/enerby/.gemini/antigravity/brain/6385c54b-84ee-4421-b647-a2334fa14922/
Contents:
- antigravity_download_page_1765309767288.webp (165KB)
- download_antigravity_1765309834119.webp (164KB)
- guia_actualizacion.md.metadata.json
- uploaded_image_0_1765263819286.png (71KB)
- uploaded_image_1_1765263819286.png (85KB)
- uploaded_image_1765309652467.png (8.7KB)
- uploaded_image_1765309951867.png (8.7KB)
- uploaded_image_2_1765263819286.png (129KB)
3. Associated Playground Directory
/home/enerby/.gemini/antigravity/playground/binary-protostar/
Status: EMPTY (only contains . and ..)
Database References
The conversation ID 6385c54b was found in:
/home/enerby/.config/Antigravity/User/globalStorage/state.vscdb(global state database)/home/enerby/.config/Antigravity/User/workspaceStorage/91466672d121e585d843fc1b1c5c71e9/state.vscdb(workspace-specific database forbinary-protostar)- Multiple log files in
/home/enerby/.config/Antigravity/logs/
Root Cause Hypothesis
The undo function appears to:
- Remove/corrupt the index entry that links the conversation to the UI
- Possibly clear the associated playground directory
- NOT delete the actual conversation data (
.pbfile) or artifacts
This suggests the bug is in the index/state management, not in data deletion.
Evidence
Screenshot 1: Conversation Missing from Agent Manager
The conversation “Antigravity Update on Pop!_OS” does not appear in the Playground sidebar, despite the data files existing.
Screenshot 2: Confirmation After Restart
After running killall antigravity and restarting the application, the conversation still does not appear.
Technical Analysis of Encryption Format
Encryption Details Discovered
| Property | Value |
|---|---|
| Algorithm | AES-256-GCM |
| Key Length | 256 bits (32 bytes) |
| IV Length | 12 bytes (standard for GCM) |
| Key Storage | GNOME Libsecret (system keyring) |
| Schema | chrome_libsecret_os_crypt_password_v2 |
Entropy Analysis
| File Type | Entropy (bits/byte) | Interpretation |
|---|---|---|
Conversation .pb files |
8.00 | Fully encrypted (maximum entropy) |
Implicit .pb files |
7.66 | Encrypted |
user_settings.pb |
4.11 | NOT encrypted (raw Protocol Buffer) |
Key Storage Location
The encryption key is stored in the GNOME system keyring with the following attributes:
label = Chromium Safe Storage
schema = chrome_libsecret_os_crypt_password_v2
attribute.application = Antigravity
Why Manual Decryption Failed
- Key derivation unknown: The raw key from keyring doesn’t directly decrypt the files
- Possible server-side component:
loadTrajectoryfunction calls Language Server, suggesting decryption may occur server-side - Additional key derivation: Likely uses PBKDF2 or similar with unknown parameters (salt, iterations)
- Per-file unique IVs: Each file has different first 12 bytes, confirming unique IVs
Code References Found
// From workbench.desktop.main.js (minified)
fwo = "mcpEncryptionKey"
OIi = "AES-GCM"
Mpc = 256 // Key length in bits
Bpc = 12 // IV length in bytes
Restoration Attempts
Attempt 1: Application Restart
- Action:
killall antigravityfollowed by reopening the application - Result: Conversation still not visible
Attempt 2: Database Analysis
- Action: Analyzed SQLite databases in globalStorage and workspaceStorage
- Finding: The conversation ID
6385c54bis referenced in workspace storage forbinary-protostar, but the UI index appears corrupted - Result: Database structure doesn’t provide a direct way to re-index the conversation
Attempt 3: Conversation File Analysis
- Action: Attempted to analyze the
.pb(Protocol Buffer) file directly - Finding: The file is encrypted/compressed and cannot be read without Antigravity’s internal decoder
- Result: Cannot manually restore or re-link the conversation
Attempt 4: Workspace Directory Check
- Action: Verified all playground directories
- Finding: All playground directories (including
binary-protostar) are empty - this is normal behavior - Result: Directory structure is not the cause
Conclusion
The conversation data exists but cannot be restored through user-accessible methods. The bug appears to corrupt the internal index that links the conversation file to the UI. A fix from the Antigravity development team is required to either:
- Provide a conversation recovery mechanism
- Fix the undo functionality to prevent this issue
Impact
- Severity: High
- Data Loss: Partial (UI access lost, but data preserved on disk)
- User Impact:
- Loss of conversation context and history
- Time wasted regenerating previous work
- Confusion about where the conversation went
Suggested Fixes
- Immediate: Add validation to the undo function to prevent it from affecting conversations when used on non-first messages
- Short-term: Implement conversation recovery mechanism that re-indexes orphaned
.pbfiles - Long-term: Add a “Deleted Conversations” or “Trash” feature to allow recovery
Additional Information
- The user was in the middle of a conversation about updating Antigravity on Pop!_OS
- The conversation contained valuable context that would need to be regenerated
- This bug appears to be reproducible (based on user report)
Attachments
- [evidencia_conversacion_existente.png](file:///home/enerby/.gemini/antigravity/brain/a954ad74-d8aa-491e-9421-62cc99ca3a0f/evidencia_conversacion_existente.png) - Screenshot showing files exist but conversation missing
- [evidencia_confirmacion_no_aparece.png](file:///home/enerby/.gemini/antigravity/brain/a954ad74-d8aa-491e-9421-62cc99ca3a0f/evidencia_confirmacion_no_aparece.png) - Confirmation after restart
Report generated: December 10, 2025 at 20:35 CST
Report generated with assistance from Antigravity AI