How can we read conversations that we’ve had with our Antigravity assistants from other programs?

Google Antigravity
1

I see Antigravity stores files in a .pb format. I’ve been trying to read it but no luck. Seems to be encrypted somehow? I’m on Windows. I wasn’t ever asked to setup an encryption key, nor do I know where one should reside.

2

Are you sure ? On my PC (windows) I have a think in my user directory somewhere a brain folder with past conversations stored as .md files, which you can read in any text editor.

3

@Patrick_van_Kemenade thank you :). Indeed the files in /brain can be used, but they are not the actual conversation. They are just artifacts produced during the run, which is still useful, but not what I’m after.

Personally, I will not use an AI assistant if I am unable to own my conversations. I consider this a basic “right”. Not even the “export” button in the Antigravity IDE is working (not that I would use it anyway, I expect my conversations to be easily accessible on the file system so that I can use them with other tools).

Kiro, Cursor, Claude Code, VS Code and OpenCode, all allow access to my conversation history. I consider this best practice.

1 Like
4

You are right, it contains a lot of .md files since I let it plan everything task + implementation plan and often afterwards it creates a walkthrough. And if sessions go big I ask for handovers.

But the actual conversation are indeed missing.

Could be usefull to have them an gather them in a local RAG or something, so you can make queries about things you did in the past and how did I fix x last time ?

So you already used 5 different AI assistents before trying out Antigravity wow thats a lot.

5

And in case you’re curious why I’m after those chats… a “little” hobby project of mine. Which I just launched officially, free & open source :slight_smile each2.ai/context-core/

@everybodyElseAroundHere , I will keep insisting that we are given the keys to the chats that we create. You’re setting a bad industry example by not documenting clearly how users of your product can own their data & hard work. As you all know, when it comes to agentic coding, the ACTUAL work is exactly these hard-written prompts & discussions. By not allowing clear & transparent access to that, it’s like you’re obfuscating our code.