Git-ignoring the .antigravitycli workspace state folder

Recently, I’ve been noticing an untracked .antigravitycli folder showing up in my Git status. I’ve seen this ever since I started using Antigravity for my personal projects—which was when the Gemini CLI stopped supporting personal accounts. I was curious: should I be committing this folder to my repository, or is it something that should be ignored?

It turns out it contains a JSON file tracking absolute paths of local checkouts and workspace permission settings (like allowWrite: true and folderUri: file:///Users/username/...). This kind of configuration is completely meaningless to be shared—it is just local state.

To get to the bottom of this, I tasked Antigravity with doing some research on itself. I had to guide it a bit because it initially gave me a very simple, high-level answer, and I wasn’t entirely convinced.

It first suggested a comparison with .vscode or .idea folders, but that’s an invalid comparison. Those directories can often hold shareable configurations (like tasks, debug launch settings, or extensions) that a team might want to version control. On the other hand, the .antigravitycli folder is strictly transient.

Here is the Anatomy of the .antigravitycli Folder:

  • Local resource tracking: It holds project resource configurations and workspace permission registries.
  • Session logs and history: It keeps trace logs for agents and local session states.
  • Transient nature: Modern versions of the Antigravity CLI register projects globally at ~/.gemini/antigravity-cli/cache/projects.json, making the local .antigravitycli directory mostly a transient runtime caching mechanism.

Because of this, the general convention is to never commit this folder to version control. To keep my git status clean, I added it to my .gitignore file:

# Antigravity CLI workspace state
.antigravitycli/

Unlike IDE config folders, all shareable configurations for Antigravity (like custom agents, skills, and rules) are stored in the .agents/ directory instead. So there is zero reason to ever commit .antigravitycli/.

That’s about it. I hope this helps keep your repositories clean when pairing with AI agents!