How to delete Antigravity conversation history, and what is left behind

use the app's Delete: a conversation is six things on disk, and even that Delete leaves its words in a database until it is vacuumed

Antigravity keeps its conversations under ~/.gemini/antigravity, beside Gemini CLI's ~/.gemini/tmp but separate from it. The transcript most tools read is only one of six things a conversation writes there, and the one Antigravity reopens is a different file. Everything below was checked on Antigravity 2.25.0, in October 2026; on Windows ~ is %USERPROFILE%.

Where a conversation is

Each conversation has an id, and four of the six places are named after it:

~/.gemini/antigravity/
  brain/<id>/                 transcript.jsonl and transcript_full.jsonl, tool output,
                              and the implementation_plan.md and walkthrough.md the agent wrote
  conversations/<id>.db       the conversation itself, the copy Antigravity reopens
                              (with -wal and -shm files beside it)
  annotations/<id>.pbtxt      its title and when you last looked at it
  presence/<id>.lock          an empty lock file
  conversation_summaries.db   one row per conversation for the list, and a full-text
                              search index holding every prompt and reply
  agyhub_summaries_proto.pb   the id, title and workspace of every conversation, in one file

So brain/<id> is not the conversation. Remove it alone and the text is still in conversations/<id>.db and in the search index, and the conversation's row in the list's database stays too.

To find an id, deja last --harness antigravity lists the conversations with their ids and first prompts. Without deja, the newest directory under brain/ is the most recent conversation, and its implementation_plan.md or walkthrough.md, if it has one, says what it was about.

Older and per-profile installs can use a differently named root, which is why deja looks under ~/.gemini/antigravity*; the terminal client agy was not checked for this page.

How to delete one conversation

Use Antigravity's own Delete: right-click the conversation in the list, or open its … menu. It asks once (“This action cannot be undone”), and then removes all six: the brain directory, the .db with its -wal and -shm, the annotation, the lock, the conversation's rows in conversation_summaries.db and its entry in agyhub_summaries_proto.pb. The workspace and the files the agent wrote into it are not touched.

Deleting by hand is the wrong tool for one conversation: its rows in conversation_summaries.db and its entry in agyhub_summaries_proto.pb, a binary file shared by every conversation, would need editing as well.

What the Delete leaves

The rows go, but SQLite does not erase the bytes they used. After Delete, the conversation's title and prompt were still readable as raw text inside conversation_summaries.db and its -wal file: not listed and not searchable in Antigravity, but there for anyone who opens the file in a hex editor or a recovery tool. To rewrite the database without them, quit Antigravity and run:

sqlite3 ~/.gemini/antigravity/conversation_summaries.db 'VACUUM;'

On the copy we tested, that removed every trace of the deleted conversation and left the others listed and searchable. sqlite3 ships with macOS and most Linux distributions; on Windows it is a separate install.

The IDE's app_storage.json (in %APPDATA%\Antigravity on Windows) also keeps the pane layout of each conversation you opened, under a key with its id. That is the id and nothing the conversation said.

How to delete all of it

Quit Antigravity, then remove the conversation stores and leave the rest of the directory, which is settings, built-in skills and the installation's own state:

cd ~/.gemini/antigravity
rm -rf brain conversations annotations presence
rm -f conversation_summaries.db conversation_summaries.db-wal conversation_summaries.db-shm agyhub_summaries_proto.pb

Antigravity starts normally afterwards with an empty conversation list, and creates all six again for the next conversation.

Do not remove ~/.gemini itself. ~/.gemini/tmp is Gemini CLI's history, and ~/.gemini/config/projects is where Antigravity keeps the workspaces you have opened.

What you lose

A deleted conversation cannot be reopened; Antigravity's own Delete says it cannot be undone. The plan and walkthrough the agent wrote live in brain/<id>, not in your workspace, so they go with it; code it wrote into the workspace stays. So does what the commands it ran did, and with the transcript gone there is no longer a record of which commands those were.

Keeping it searchable instead

deja reads Antigravity's transcripts, alongside the other agents' histories, into one local index:

curl -fsSL https://raw.githubusercontent.com/vshulcz/deja-vu/main/install.sh | sh
deja "the Antigravity conversation about the migration"

Indexing and search stay local and credentials are stripped. A conversation deja has already indexed stays searchable after Antigravity deletes it, and deja forget removes it from the index when you want it gone there too. What deja cannot do is put it back into Antigravity: the app reopens a conversation from conversations/<id>.db, which deja does not read, so deja does not write an Antigravity conversation back. Index before deleting, not after.

Where every agent keeps its history · Memory for Antigravity · The same question for Gemini CLI · The Antigravity format

Found this useful? Star deja-vu on GitHub.