Three ways to keep a chat record when the Export button does nothing

Picture an evening when you press Export and nothing happens. No dialog, no file, not even an error line. The conversation behind that button holds hours of design discussion.

First, a note on scope. I could not reproduce the real export bug myself. What I did verify is the backup script further down, run against a stand-in folder. The symptom itself has several reports on the official forum, so I will keep "what people report" and "what ran on my side" clearly apart.

The reported symptoms are similar, but not identical

Reading the forum, several people describe pressing the button with no file and no error. Some say it broke right after an update. Others say the command palette's export does nothing either, and one report mentions 0-byte Markdown files. So there is probably more than one failure.

Some people can still see their history and only the export fails. Others cannot see the history in the list at all. It helps to treat those two separately.

Route 1: ask the agent to write the conversation out as Markdown

One forum report says that asking the agent to export the whole chat as a Markdown file worked. The same report adds a catch: if the conversation was already truncated, only the truncated part comes out.

So ask early, at a natural break, not after the thread has grown huge. A short request is enough.

Please write what we have so far into docs/chat-notes-YYYYMMDD.md as Markdown,
split into: decided, parked, and next steps.

I split it into three parts because a list of decisions is what I reopen most often as an indie developer, far more than a full transcript.

Route 2: copy from the screen into your own notes

It is plain, but it is the most reliable. Even when export is broken, the text on screen can be selected and copied. Paste the important answers into a dated file.

The weakness is that it is manual. I would not keep it up for every reply, so I limit it to two kinds: answers that settled a design, and commands that actually worked.

Route 3: snapshot the chat folders with a date stamp

Several forum reports say the history was gone from the screen while the data was still in a local folder. The places mentioned were under .gemini/antigravity in the home directory, including brain, and some people found conversation files (.pb).

One caution: these locations come from user reports, not from an official specification, and they may differ by version. Check that the folder exists on your machine first.

ls -la ~/.gemini/antigravity

If it exists, snapshot it with the script below. It solves one problem: having a plain copy before an update or a bug hides your history.

#!/usr/bin/env bash
set -euo pipefail
 
SRC="${AG_DIR:-$HOME/.gemini/antigravity}"
DEST="${AG_BACKUP_DIR:-$HOME/ag-chat-backup}"
STAMP="$(date +%Y%m%d-%H%M)"
 
[ -d "$SRC" ] || { echo "not found: $SRC" >&2; exit 1; }
mkdir -p "$DEST"
 
# Only conversations and brain; other settings are left out on purpose
tar -czf "$DEST/ag-$STAMP.tar.gz" -C "$SRC" conversations brain
 
# Keep the newest 14 and delete older ones
ls -1t "$DEST"/ag-*.tar.gz | tail -n +15 | xargs -r rm --
 
echo "saved: $DEST/ag-$STAMP.tar.gz"

Three reasons for the shape. set -euo pipefail prevents a "saved" message when the folder was never there. Limiting the archive to conversations and brain avoids pushing other files, which may hold credentials, into a synced cloud folder. Capping at 14 keeps daily runs from growing without bound.

I ran it against a stand-in folder containing only conversations/a.pb and brain/abc/, and confirmed the archive held both. I did not run it against a real Antigravity folder.

The xargs -r and tail -n +15 pairing assumes GNU tools. The stock xargs on macOS may not have -r, and in that case it is safer to drop the cleanup line and tidy old archives by hand.

Restore somewhere else first

When you unpack a snapshot, do not extract over the real folder. Unpack into a separate directory and look at it.

mkdir -p ~/ag-restore-check
tar -xzf ~/ag-chat-backup/ag-YYYYMMDD-HHMM.tar.gz -C ~/ag-restore-check
ls -R ~/ag-restore-check | head -20

One forum user reports getting chats back by copying conversation files into the newer folder. That is unofficial, so take a snapshot before copying anything. Once you overwrite, there is no road back.

Where I draw the line

Whether export works can change from version to version. A second copy of your own record, on the other hand, is something you can always keep.

Never rely on a single way out; keep two routes to your record. I intend to hold to that even after the button is fixed.

Today, I would start with one line: ls -la ~/.gemini/antigravity. Whether the folder exists tells you which route to take.