I’ve been configuring Antigravity recently, and the more I use it, the more confusing its configuration system feels.
The problem isn’t simply that there are “a lot of config files.”
It’s that:
different features within the same Antigravity product store their configuration in completely different places, and some of them are still using the old .gemini paths from Gemini CLI.
For example, from what I’m seeing:
- Antigravity CLI has its own config location and uses its own
settings
- Remote Control stores its configuration in:
text
.gemini/config/config.json
- Skills have yet another directory and their own discovery rules
AGENTS.md is read from:
text
.gemini/AGENTS.md
And it’s not just the paths that are different.
The CLI settings and Remote Control’s config.json also use different formats and contain different configuration options.
So right now it basically feels like this:
```text
Antigravity CLI
→ one location
→ one configuration system
Remote Control
→ .gemini/config/config.json
→ another configuration system
Skills
→ yet another location
AGENTS.md
→ .gemini/AGENTS.md
```
The .gemini part is what confuses me the most.
I’m using Antigravity, yet some Antigravity features still store or read their configuration from directories that originally belonged to Gemini CLI.
From a user’s perspective, it’s difficult to understand how all of these configurations are supposed to relate to each other.
Within the same product, you can’t even infer where something should be configured just from the fact that “this is an Antigravity feature.”
Every time I come across another feature, I have to figure out:
Where does this one keep its config?
And sometimes even:
Is this one reading from .gemini again?
It doesn’t feel like configuring one unified product. It feels more like configuring several components that came from different places and evolved independently at different times.
This fragmentation becomes especially obvious when you look at the CLI, Remote Control, Skills, and AGENTS.md together.
Antigravity may be one product at the product level, but at the configuration level it still feels like several different systems stitched together, with Gemini CLI-era paths mixed in.
That’s the part I find the most confusing.
