Frustrated with aggressive context compaction before plan execution

Google Antigravity
1

Hi team,

I am writing to express my frustration with the current context compaction behavior. Every time I prepare a detailed implementation plan and transition to execution, the system compacts the history, wiping out a significant amount of the context I just established.

The biggest advantage of Gemini models is their massive 1M+ token context window. Aggressively compacting the history right when execution starts completely defeats this strength. It is highly frustrating to plan using Claude models, only to have the entire context destroyed by compaction the moment execution begins.

The context limit before compaction needs to be increased. At the very least, it must be large enough to preserve the plans and the immediate context so the model remains fully aware of the project state during execution.

Thanks.

2

I think you might be onto something there ! After transitioning from Gemini to Antigravity I’m still understanding the very different architecture compared to Gemini. See Architectural Strategy and Setup Guide for Apple Application Development in Google Antigravity -The Technical Contrast Between Gemini CLI and Antigravity CLI Architecture

This has caused me significant issues. I’m used to the linear Gemini CLI, not the mixture of agents paradigm of Antigravity. I have spent long sessions with Gemini CLI working through product design, architecture and philosophy of a product. It remembered everything. But not with Antigravity. Maybe I just need to adapt to the architecture.

Can someone from Google verify that the context window is an issue ?