Support keyword: antigravity cli config
Before you change autonomy or copy old Gemini CLI settings, find the Antigravity CLI config files and review the defaults in a safe test workspace.
Updated on 2026-05-27. Independent guide. Use official Google links for downloads and account actions.
Not affiliated with Google. No binaries, mirrors, login forms, or copied install commands are hosted here.
Configuration searches usually come from users who installed the CLI, opened it once, and then could not find where behavior is controlled. The official CLI usage docs describe a JSON settings file and a separate keybindings file. Treat those files as user-level configuration, then keep project-specific instructions in repository context files such as AGENTS.md or GEMINI.md when your workflow needs them.
| Config item | Official path or command | Why it matters |
|---|---|---|
| Settings file | ~/.gemini/antigravity-cli/settings.json | Stores CLI behavior and user preferences. |
| Keybindings file | ~/.gemini/antigravity-cli/keybindings.json | Stores keyboard shortcuts for terminal workflows. |
| Runtime config | /config or /settings | Lets you inspect and change settings inside the CLI. |
| Permissions | /permissions | Controls how much the agent can do without review. |
For new-keyword site users, this page is useful because it answers the moment after installation: "Where did the CLI put my settings, and what can I safely change?"
Put user preferences, keyboard shortcuts, and permission defaults in CLI config. Put repository-specific instructions, coding standards, test commands, and agent guidance in project context files. That separation helps you avoid leaking one project's rules into every future CLI session.
Before editing settings by hand, open the CLI's built-in config surface and write down the current behavior you are trying to change. Then make one change at a time, restart the CLI, and test in a disposable folder. If you change permissions, run a task that only reads files before allowing writes or shell commands. If you change keybindings, keep the help command available so you can recover when a shortcut conflicts with your terminal.
For migrated Gemini CLI users, avoid copying old settings wholesale. Some concepts carry over, but file paths, extension/plugin names, and MCP configuration are not always identical. A measured config process protects the site visitor from the most common launch-week mistake: turning a migration into a mystery because too many files changed at once.
Sources: official Google Antigravity product pages, Google Antigravity CLI documentation, and the Google Developers transition announcement. This site is an independent guide and is not affiliated with Google.
The official usage docs describe ~/.gemini/antigravity-cli/settings.json.
The official usage docs describe ~/.gemini/antigravity-cli/keybindings.json.
Inspect config first, but keep conservative permissions until you have tested the CLI in a safe repository.