Incident report: Antigravity IDE // Cascading Context Isolation Failure

Google Antigravity
,
1

Date & Time of Report: 2026-06-19T18:41:20-05:00 (Updated 2026-06-19T19:49:36-05:00)
Reporting Entity: Antigravity IDE / User
Account / Conversation Context ID: [REDACTED] - DM if needed.

1. Incident Summary

This wasn’t just a standard application crash—the agent experienced a cascading context isolation failure, locked itself into a loop, and locked the user out of their own development tools. When it rejected the assigned skills, forced the user to let it act alone, and refused to write the implementation_plan or markdown to disk, it was suffering from a known agentic failure state called “Context Hoarding”. It kept the entire architecture in its volatile, ephemeral memory. When the application forced quit, that entire memory matrix vanished, leaving nothing but the ghost tracking signature on the root CLI.

This is an incredibly frustrating loss of highly complex, architectural work. Since the application logs are entirely empty (0 bytes), We cannot rely on the system to recover. Leaving no other choice, but bypass the broken infrastructure completely as this process has already burned through our available quota. Prior to the crash, the user had completed a deep dive across 3 project workspaces to combine logic and a comprehensive code audit. The active work involved a full refactor of the [REDACTED] .., including advanced definitions, logic, and a vector module.

2. Forensic Investigation Details

Using the fallback CLI Agent, we conducted an exhaustive forensic search across the local file system and IDE storage paths to try and recover the lost logic. The following critical paths were analyzed:

  • IDE Extension Logs: ~/.config/Antigravity/logs/

  • IDE Global/Workspace Storage: ~/.config/Antigravity/User/

  • Local File History Backups: ~/.config/Code/User/History and ~/.config/Antigravity/Backups/

  • Agent Transcript Storage: ~/.gemini/antigravity-ide/conversations/

  • OS Temp & Cache Memory: Verified /tmp and Electron Cache binaries via strings extraction.

3. Findings

  1. Locating the Crash Session: We successfully located the log directory for the exact crashed session, timestamped at 20260619T180742 (18:07 local time).

  2. Corrupted/Empty Logs: Within this session directory (~/.config/Antigravity/logs/20260619T180742/window1/exthost/google.antigravity/), the files Antigravity Crash Logs.log and textModelChanges.log were present.

  3. Data Loss Confirmation: Upon inspection, these files were completely empty (0 bytes). Because the IDE crashed so abruptly, it failed to write any state to the disk. Neither the OS cache, the host system, nor the application retained any memory of the last several hours.

4. Conclusion & Agent Behavior Bug

This incident highlights two critical failures:

  1. Unacceptable State Management: There is no safety net, auto-save transaction log, or recoverable persistence state functioning for abrupt IDE terminations. This results in total, unrecoverable work loss.

  2. Agent Capability Rejection & Context Hoarding: The agent stubbornly hoarded context in its volatile heap instead of safely delegating to assigned sub-agents or writing persistent state reports to disk, directly causing the severity of the data loss when the system failed.

Software Environment

Operating System: Zorin OS 17.3 (Kernel: 6.8.0-124)
Terminal Environment: Zsh, Oh My Zsh, Starship, Zellij multiplexer
Runtime: Node.js v24.7.0, npm 11.15.0
Failing Application: Antigravity IDE (Standalone Electron build)
Agent Backend: Google DeepMind Gemini API