Severity: 
CRITICAL — Data Loss
Environment
- OS: macOS (Mac Mini, Apple Silicon)
- Antigravity version: 1.20.5 (auto-updated this morning, March 11 2026)
- Previous version: Working fine before auto-update
Bug 1: All New Conversations Lost After Restart (DATA LOSS)
After updating to 1.20.5, every new conversation is corrupted and cannot be recovered when Antigravity is closed and reopened. The conversation history shows the conversations existed, but their content is gone — they cannot be loaded, resumed, or recovered.
This is a data loss bug. Hours of work across multiple conversations have been permanently lost.
Steps to reproduce:
- Update to Antigravity 1.20.5 (auto-update)
- Start a new conversation, do significant work
- Close Antigravity completely (Cmd+Q)
- Reopen Antigravity
- Result: New conversations created in 1.20.5 are corrupted — content is missing/unrecoverable
What I’ve tried (none worked):
- Restarting Antigravity multiple times
- Ran AG-Chat-Recovery tool — could not recover the corrupted conversations
- Checked
~/Library/Application Support/Antigravity/— data files exist but appear corrupted
Bug 2: Export Completely Broken
The Export function does not work at all in 1.20.5. Clicking the Export button produces no response — no dialog, no file, no error. This is the same issue reported by @anton_jr on Windows 10, confirming it is a cross-platform regression introduced in 1.20.5.
Steps to reproduce:
- Open any conversation (existing or new)
- Click the Export button
- Nothing happens — no dialog, no file generated, no error message
What I’ve tried (none worked):
- Cmd+Shift+P → Antigravity: Export Conversation — no response
- Cmd+Shift+P → Antigravity: Restart Agent — export still broken after restart
- View → Output panel — completely empty when export is triggered
Impact
These two bugs together create a catastrophic workflow disruption:
- Cannot save work — new conversations are silently corrupted on restart
- Cannot export work — no way to manually back up conversation content
- No warning — the auto-update applied silently; users had no chance to opt out
- No rollback mechanism — no built-in downgrade option; Backups folder is empty
I have lost multiple critical work conversations today that contained important technical decisions and code. This data is unrecoverable.
Expected Behavior
- Conversations should persist across restart without corruption
- Export should produce a .md file or show a save dialog
- Auto-updates should not introduce data-loss regressions
Request
- Immediate hotfix for conversation persistence and export
- Provide a way to download previous versions (1.20.3 or earlier) from the official site
- Add a setting to disable auto-updates or at minimum prompt before applying
- Consider rollback capability when critical bugs are detected post-update
Workaround (for other affected users)
Before doing anything, back up your data.
Update: After downgrading to 1.19.6, all “lost” conversations from 1.20.5 are now visible and accessible again. This confirms the data was never actually corrupted — 1.20.5 simply cannot read its own conversation data after restart. The underlying storage is intact.
