Copied to Clipboard
Here I am specifically asking it to plan it out first. It comes back saying:
I have created the implementation plan for the Google Cloud Run greeting application.
Please review the proposed design and files in the implementation_plan.md artifact. Once you approve, let me know and we will proceed to verify it.
This behind the scenes creates:
~/.gemini/antigravity-cli/brain/11111111–2222–3333–4444–555555555555/implementation_plan.md
Depending on how you proceed, additional markdown files (walkthrough, task list, etc) will be created in the same folder.
As an experiment, go ahead with approving the implementation plan. This will make Antigravity CLI generate the code, test out the server, etc. This will result in additional folders being created but all within the brain/CONVERSATION_ID folder.
If you navigate to your app data folder during/after a coding conversation, here is exactly what you would start seeing something like this:
~/.gemini/antigravity-cli/
└── brain/
└── 11111111–2222–3333–4444–555555555555/ ← Root of the conversation
├── .system_generated/
│ └── logs/
│ ├── transcript.jsonl ← Truncated log
│ └── transcript_full.jsonl ← Untruncated full log
├── implementation_plan.md ← Technical design spec
├── task.md ← Interactive checklist
└── walkthrough.md ← Work summary & verification
A few other things worth mentioning are:
- You will find a history.jsonl within the ~/.gemini/antigravity-cli folder that seems to be a index of all conversations.
- A conversations folder that holds the conversations in a protocol buffer format. We can leave it as is for now.
Let’s Rewind
What if we want to go back at a point in time in the conversation. Remember we started with asking about Google Cloud Run, then we asked it to generate code for the application and so on. As a result of which, several code files, artifacts etc have been generated.
If I go into shell mode and see the current files in the folder, you can see from the output below, the files that are currently present. So far so good.
●くろまる ! ls
⎿ Dockerfile
node_modules
package-lock.json
package.json
public
README.md
server.js
Now, give the /rewind command and you should see a list of all interactions that you have had. In my case, you see the current conversation thread with the list of interactions. I can use the keyboard to go up at the specific point in time before the files were generated (8 files changed, etc).
──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
Rewind Conversation
What is Google Cloud Run?
> What kind of applications can I deploy on Google Cloud Run?
Create a single page HTML / JavaScript application to deploy on Cloud Run tha...
8 files changed +583 -1
Could you first plan it out?
1 artifact generated
what is the history.jsonl file that you are managing for the conversations
what is a .pb file and how are you using it for conversations
(current)
Keyboard: ↑/↓ Navigate enter Select esc Cancel
Once I select to rewind it to a step before all the files were generated and execute that step, it will remove the files generated as is evident from the outputs that I now see.
●くろまる ! ls
⎿ node_modules
package-lock.json
public
The implementation_plan.md and other artifact files also go away from the brain/CONVERSATION_ID folder that we earlier saw. You can try out these scenarios on your machine.
Saving a Conversation with a different name
At any point in time, you can save the conversation with a name that is easier or makes sense to you in terms of the entire thread. Just use the /rename command.
In Antigravity CLI, I simply give the rename Google Cloud Run basics to rename this conversation. It comes back with the following message:
> /rename
⎿ Conversation renamed to: Google Cloud Run basics
Switching between Conversations
You can use the /resume or /switch command to switch to another conversation. For example, I see the following:
CLI Antigravity (tab to cycle)
Conversations
Type to search...
> [CURRENT] Google Cloud Run basics 10 steps 8m ago
Understanding Antigravity CLI Conversations 24 steps 52m ago
hello 4 steps 1h ago
Keyboard: ↑/↓ Navigate ←/→ Page enter Select f2 Rename ctrl+delete Delete tab Switch Tab esc Go back / Clear search
You can see that our current context is now with our preferred name Google Cloud Run basics and the other ones that you see in the list are the ones that I had here. But you might see another list.
Select any one of these to switch to that conversation and carry on that conversation from there or maybe even rewind, etc.
Switching to an Antigravity conversation
If you have been paying attention to the output shown in the /switch command, you might see an Antigravity and CLI option. This might happen only if you have also installed the non-CLI option i.e. Antigravity on your machine. In my case I have and have interacted a bit with it.
But what is pleasantly surprising is that it is now showing me conversations that have been saved via Antigravity and allowing me to import them. Whew! Let’s try this out:
CLI Antigravity (tab to cycle)
Conversations
Type to search...
> Extracting Invoice Information [Import this conversation? (y/n)] 20 steps 2h ago
Generate a events website but let's discuss the requirements first. 67 steps 1d ago
Keyboard: ↑/↓ Navigate enter Select tab Switch Tab esc Go back / Clear search
So I select one of the conversations (Extracting Invoice Information) and then press on Enter. It asks me that it needs to import this conversation. This brought up the previous conversation and I was able to carry on with a new message in the thread. Wonderful. Probably this needs a lot more testing.
<PREVIOUS _ CONVERSATION _ THREAD >
────────────────────────────────────────────────────────────
> What are the files sizes for each of the invoices
●くろまる ListDir(/Users/romin/agy-cli-projects/invoice-processing) (ctrl+o to expand)
Here are the file sizes for each of the invoice image files in your directory:
• inv1.png: 273,828 bytes (approx. 273.8 KB)
• inv2.png: 369,086 bytes (approx. 369.1 KB)
• inv3.png: 446,932 bytes (approx. 446.9 KB)
• inv4.png: 343,328 bytes (approx. 343.3 KB)
(Note: The CHUBB.pdf insurance document size is 42,965 bytes / approx. 43 KB).
One more thing
If you quit your Antigravity CLI at this point, you will notice that there is a message at the end that looks something like this:
Resume: agy --conversation=d1d8a55b-cc27-4dd4-bc62-2f73015960d2 (or -c)
That’s right. Antigravity CLI comes with a command line option to resume a specific conversation via the --conversation or -c parameter. This value has to be the unique conversation id that you see. I think this is useful but might be a bit unwieldy to remember or use.
In any case, the key message is that you now what is going on with this unique conversation id , where the stuff is persisted on your local machine and can discover more. In any case, you can always launch Antigravity CLI and use the /switch command to go to a specific conversation thread. Just remember to use /rename to name them in a way that you understand.
Conclusion
While a conversation in Antigravity CLI is something that is managed behind the scenes for you, it is helpful to understand how the tool is working. Hopefully these examples give you a good idea of what is happening under the hood. I will keep adding more examples to this as I understand this better. See you in latter parts of the series.