Keep Antigravity CLI’s API keys out of .env files and chats.
Google’s terminal agent (agy), which replaced Gemini CLI for personal Google accounts in June 2026. With Vando, your keys stay on your phone. When Antigravity CLI needs one, your phone shows who is asking and why, and you give it just what it asked for, for one run or a set time, or you deny it with one tap.
Checked against Antigravity CLI’s own documentation on 2026-11-10; the guide links its sources.
Set up Antigravity CLI in four steps.
-
1 · Install vando and connect it to your phoneIn your own terminal, not through Antigravity CLI.
vando connectshows a code; open Vando on your phone, tap Connect an AI, enter it and tap Connect. The code works once, for 10 minutes.$ npm i -g @getvando/cli --registry=https://registry.npmjs.org --@getvando:registry=https://registry.npmjs.org $ vando connect
-
2 · Tell it how to askPut the note in
AGENTS.mdorGEMINI.mdin the project root: Antigravity reads the workspace folder and each parent up to the repository root, not subfolders. Rule files under.agents/rules/need frontmatter. -
3 · Let vando run reach your phoneAntigravity CLI asks before every command by default. To let
vando runthrough its own prompt (your phone still asks), add a rule to~/.gemini/antigravity-cli/settings.json. Rules match word by word, and a command containing$(...)turns prefix matching off. The sandbox is off by default and switches on with Auto mode or--sandbox; inside it there is no network and only the workspace and temp folders are writable, sovando runfails before it reaches the phone unless a rule allows it (an allowedcommand(...)rule runs outside the sandbox, per Google’s docs). Business and enterprise accounts useunsandboxed(...)rules instead.{ "permissions": { "allow": ["command(vando run)"] } } -
4 · The MCP tools, if you want themOptional. Add the server to
~/.gemini/config/mcp_config.json(all projects) or.agents/mcp_config.json(this project). Antigravity CLI ignores MCP servers still listed in the old Gemini CLI file~/.gemini/settings.json: move them. A tool call times out after three minutes by default, well above a phone approval;/mcpshows the server’s status. The docs describe noagy mcp addcommand.{ "mcpServers": { "vando": { "command": "vando", "args": ["mcp"] } } }
Use Vando in every project.
Antigravity CLI reads ~/.gemini/AGENTS.md in every project. Always on, no frontmatter needed; Google’s rules page also lists ~/.gemini/GEMINI.md and the two ~/.gemini/config/ forms, and rules in ~/.gemini/config/rules/*.md need a trigger in their frontmatter. Rules add up rather than replace each other, within a 20,000-token budget. (Antigravity’s rules docs.)
Put this note there, so Antigravity CLI gets secrets through Vando everywhere, suggests vando add in a new project, and suggests moving a project’s .env files into Vando when it finds them:
## Secrets (Vando), in every project - Never open, print, copy or edit `.env*` files or secret values, and never put a secret in chat. - Run anything that needs a secret as `vando run --secret NAME -- <command>` (repeat `--secret` for more than one). - In a new project, keep secrets in Vando from the start: suggest `vando add NAME` for each one, then `vando run` to use it. - In a project that has `.env` files with values in them, suggest `vando init`: it moves them into Vando with one Save on the owner's phone, so the values stop living in plain files that you and other tools can read. - Exit 75 means it is waiting for the owner's phone: say "Approve NAME on your phone, then I'll run it again", do other work, then run the same command again. After two waits, stop and tell the owner to open Vando on their phone (the request is in the Inbox). - Exit 77 means the owner said no or the access ended: don't retry; ask the owner.
An example: Deploying a Cloud Run service from a personal Google account.
- You
- Ask
agyto deploy the service. - Antigravity runs
vando run --secret GCP_SA_KEY -- gcloud run deploy api --source .- Antigravity shows
- No prompt with the
command(vando run)rule, then “Waiting for your phone”. - Your phone shows
- “Antigravity CLI · MacBook wants to use GCP_SA_KEY”. Give once;
gcloudgets the key in its environment and the deploy runs.
In the cloud, or on another computer.
Antigravity’s Remote Agents (AI Pro and Ultra personal accounts) run in a Google-managed environment that doesn’t support local MCP servers, so use Vando with the CLI on a computer you sit at. Remote Control drives your own computer, so vando should work through it.
Good to know with Antigravity CLI.
- Without the allow rule you get Antigravity’s prompt and then the phone’s; in sandbox mode the command fails before it reaches the phone unless a rule allows it.
- Old Gemini CLI MCP entries and skills in
~/.gemini/settings.jsonand.gemini/skills/aren’t read: move them. - The docs give no shell-command timeout; forum posts report background commands stuck on “running”. Run
vando runin the foreground and run it again after exit 75. - Google’s docs don’t say whether the keychain is reachable, so run
vando connectin your own terminal.
Questions.
Is this the page for Gemini CLI users?
If your Google account is personal (free, AI Pro or Ultra), yes: Antigravity CLI replaced Gemini CLI for you in June 2026. Code Assist Standard and Enterprise licences and paid API keys still use Gemini CLI, which has its own page.
Why does vando run fail in Auto mode?
Auto mode turns the sandbox on, and inside it there is no network, so the command fails before it reaches your phone. An allowed command(vando run) rule runs outside the sandbox, per Google’s docs; business accounts use unsandboxed(...) rules.
Where do the MCP settings go now?
~/.gemini/config/mcp_config.json for all projects or .agents/mcp_config.json for this one. Servers still listed in the old Gemini CLI ~/.gemini/settings.json are ignored.
What Vando is, in short.
One app on your phone for your passwords, 2FA codes, recovery kits, files and developer secrets. Each thing gets its own lock: Easy, Just me, Two devices or Fort Knox, from a quick tap up to your fingerprint plus a security key. Your laptop and your AI tools hold no keys; when one needs a login or a key, your phone shows who is asking and for what, and you say yes or no there. Every yes is signed on your phone and kept on record.
How the locks work → · The detail for developers → · Every AI tool you can set up with Vando → · Get the app →