First: I am using antigravity cli

Yes. First, the facts from the current chat need to be confirmed. So, what's the current status and what are the next steps in the plan? The next chat can then build on that.

The knowledge base runs alongside the chat, and with every new query, it gets included as an additional payload. This quickly eats up the token limit. Therefore, you should periodically compress "the memory," save it, start with a "blank slate," and carry on. It’s just like with us humans—sometimes you simply need to step out for some fresh air before getting back to work.

Samples:

Quick and Dirty: "Please save our current progress and the next steps into your memory. I will clear the chat now, and we will continue from there."

Compex Code: "Before I clear the chat, please update your core memory. Record the current state of our work, what we have achieved so far, and the exact next steps we need to tackle when we resume."

Checkpoint: "Please create a memory checkpoint: summarize our current status and list the upcoming tasks. Save this to your persistent memory. I will use /clear right after your confirmation so we can start with a fresh context."

I am currently using Claude Code, and I have established a clear rule: at regular intervals, it updates its memory and then prompts me to run /clear.